Re: [libmicrohttpd] Weird URL parsing behaviour

[Christian Grothoff]

Hi David,

I've modified the "daemontest_process_arguments.c" testcase
(src/testcurl/) to specifically include the "%A0"-escaping case you
mentioned and strengthened the test to check for spurious arguments
appearing in SVN 26254.  However, the test still passes without problems.

As you're not reporting which MHD version you're using, it is of course
conceivable that this is a historic issue; alternatively, I'm simply
doing something wrong when trying to reproduce the issue/bug.

Could you look at the test and see if you can modify it further to make
it trigger the issue? The code is doing a pretty straightforward GET
request and mostly only checks the arguments.


Happy hacking!

Christian


On 02/28/2013 04:24 PM, David J Myers wrote:
> Hi there,
> 
> When I send the following URL into my libmicrohttpd based embedded
> web-server, I don't receive the url correctly inside my
> http_access_callback.
> 
>  
> <http://10.26.7.81/events/CreateAlarmEvent.cgi?id=1&trigger=1&SetOutput=0&Ou
> tputActiveHigh=0&duration=1&SendFrame=0&SendTCPMessage=1&TCPMessageString=Zo
> ne1%A0triggered&StreamIndex=0&maxfps=1>
> http://10.26.7.81/events/CreateAlarmEvent.cgi?id=1&trigger=1&SetOutput=0&Out
> putActiveHigh=0&duration=1&SendFrame=0&SendTCPMessage=1&TCPMessageString=Zon
> e1%A0triggered&StreamIndex=0&maxfps=1
> 
> The TCPMessageString parameter contains two non-breaking-space characters
> (&NBSP = 0xA0) and the effect of this is that I get an extra parameter in
> the callback url which is the last 3 characters of this parameter, ie the
> string "red".
> 
> I assumed that &NBSP characters are normal in URLs, so I don't understand
> what is happening here.
> 
> Best regards, David
> 
>