4 messages in ru.sysoev.nginxRe: Requests with full URIs
FromSent OnAttachments
James OakleySep 24, 2007 7:26 am.patch
Igor SysoevSep 24, 2007 12:43 pm 
James OakleySep 25, 2007 10:44 am 
Igor SysoevSep 26, 2007 4:29 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Requests with full URIsActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Sep 24, 2007 12:43:52 pm
List:ru.sysoev.nginx

On Mon, Sep 24, 2007 at 11:26:29AM -0300, James Oakley wrote:

I've noticed that Nginx supports full URIs in requests, which is great, since I need to be able to respond to proxy requests.

I have noticed one problem, though. If I request a URI like so:

curl -x 127.0.0.1:80 http://www.google.com/

It works, and I get the correct response (I'm using empty_gif to test this)

If I leave the trailing slash, however, I get a 400 instead:

curl -x 127.0.0.1:80 http://www.google.com <html> <head><title>400 Bad Request</title></head> <body bgcolor="white"> <center><h1>400 Bad Request</h1></center> <hr><center>nginx/0.5.31</center> </body> </html>

I have attached a patch that appears to fix the problem, but I have only just started looking at the code and I have no idea whether this was the correct way to fix it.

How does Apache treat this request ?

-- Igor Sysoev http://sysoev.ru/en/