Re: [cgi-devel] post data with illegal characters
Status: Beta
Brought to you by:
drrngrvy
From: Darren G. <dar...@gm...> - 2011-01-12 02:00:46
|
Hi Jean-Christophe, On 12 January 2011 01:42, <jc...@ol...> wrote: > Hello Darren > > I am still struggling with that issue. I know for sure the problem is the > presence of nul terminators at the two ends of post values. > > I must apologize because I have not yet put together a little program > showing the issue. I really like your library (and I use it) and I would > like to hep you a bit. > > Par of the problem is that I noticed the issue when getting post values > from the upload of file throug nginx and the nginx_upload_module. This > module allows the upload of the file to be done by nginx and, once the > file on the server, the request is transferred from the nginx module to > the fascgi backends. To make it harder to write a small code, I was also > using plupload on the client side to manage the upload od several files at > the same time. > I have a little function that cleans the null terminators from every post > value that is used by my program, which solves the consequences of the > problem but is not a satisfactory solution. > > Let me revisit the issue and produce something useful to track the issue. Thanks for looking into this. I've only done very cursory testing with nginx so far, but since that's quite a slick server I'd very much like to support it* without users like yourself needing any hacks. Is it possible that the server is sending extra data to the FastCGI backend and expecting the script to check some meta-data in the form data? Just a stab in the dark really. If you are able to get the complete POST'd data from request.post_data(), dump it to a file and send me it (off-list if you prefer) I can take a look at it. Sorry I can't help more. Cheers, Darren * There were rumours of a multiplexing FastCGI module for nginx, which would be very very nice to get my hands on, if that ever surfaces. |