All files from this thread

File Name File Size   Posted by Date  
nginx-0.8.49-uri_percent.patch 1.1 KB open | download Matthieu Tourne 09/28/2010 Read message
Peter Portante
June 11, 2010 04:12PM
Hi Igor,

This is working great. Thank you!

Should we be prepared to maintain this as a patch on the 0.8 stream, or
would some variation of this fix be folded into 0.8 (via some config setting
or as the new behavior)?

And while we are at it, how stable is 0.8? I thought I had seen some
discussion of 0.8 being marked "stable" soon. Just curious.

Thanks,

-peter


On 6/11/10 4:09 AM, "Igor Sysoev" <igor@sysoev.ru> wrote:

> On Fri, Jun 11, 2010 at 02:54:35AM -0400, Peter Portante wrote:
>
>> Hi Folks,
>>
>> We are running into a small problem with bad HTTP clients.
>>
>> We have sold a bunch of hardware with embedded HTTP clients which don't
>> URL-encode the parameter values. For example:
>>
>> GET /a/r?did=X234 567 Y HTTP/1.1
>>
>> We were using a pair of Apache servers behind a hardware load-balancer and
>> switched our environment to front those Apache servers with a pair of Nginx
>> servers. We actually use those Nginx servers for a number of other web sites
>> we serve.
>>
>> When we made this switch, these particular clients stopped working. Nginx is
>> responding immediately after receiving the "GET" line above with "400 Bad
>> Request". This *is* valid behavior on Nginx's part, as according to our
>> understanding of the HTTP protocol, no spaces are allowed in the request
>> URI.
>>
>> Apache is apparently rather forgiving on this front. Is there some setting
>> or configuration parameter in Nginx that would make it more forgiving of
>> these spaces in the request URI?
>>
>> If there is not, would it be difficult for us to modify Nginx to make it
>> more forgiving? If so, any pointers as to where to start?
>>
>> Our other options we can think of are:
>>
>> 1. route HTTP traffic from these clients to Apache servers
>> 2. leave them dead in the water until customers complain so we can tell them
>> to upgrade their firmware for the fix
>>
>> Thanks for any help or pointers you can offer.
>
> Try the attached patch against 0.8.40.
>



_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

spaces in URI

Igor Sysoev June 11, 2010 04:14AM

Re: spaces in URI

Peter Portante June 11, 2010 04:12PM

Re: spaces in URI

Igor Sysoev June 11, 2010 04:40PM

Re: spaces in URI

Peter Portante June 11, 2010 05:00PM

Re: spaces in URI

cgarver September 28, 2010 10:24AM

Re: spaces in URI

cgarver September 28, 2010 10:35AM

Re: spaces in URI Attachments

Matthieu Tourne September 28, 2010 12:06PM

Re: spaces in URI

cgarver September 28, 2010 12:38PM

Re: spaces in URI

Matthieu Tourne September 28, 2010 12:50PM

Re: spaces in URI

Igor Sysoev September 28, 2010 01:00PM

Re: spaces in URI

cgarver September 28, 2010 01:06PM

Re: spaces in URI

cgarver September 28, 2010 01:24PM

Re: spaces in URI

cgarver September 28, 2010 01:37PM

Re: spaces in URI

cgarver September 28, 2010 01:41PM

Re: spaces in URI

cgarver September 28, 2010 02:14PM

Re: spaces in URI

cgarver September 28, 2010 02:41PM

Re: spaces in URI

Igor Sysoev September 28, 2010 01:20PM

Re: spaces in URI

Igor Sysoev September 28, 2010 01:30PM

Re: spaces in URI

Igor Sysoev September 28, 2010 02:04PM

Re: spaces in URI

Igor Sysoev September 28, 2010 02:22PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 295
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready