-
-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using request absolute URI Thin leaves PATH_INFO empty #8
Comments
Indeed, it's a known bug (or unsupported feature if you will). Web browsers never use absolute urls so it's an edge case. Why are you sending this request? |
Thanks for the response. I don't use Thin for web applications but for XCAP (RFC 4825) which is XPath over HTTP (more or less). It's still a new protocol and I don't know if vendors will implement relative or absolute URI's in the HTTP requests (I expect they will always use relative uri however). So I have seen no http client using absolute uri yet. |
I can't believe nobody else runs into this problem when using thin in conjunction with the proxy.pac file?! In which case Rails ends up serving the root page to all requests (including assets).
|
I experienced this issue too. |
It should be fixed on v2 branch or gem install thin --pre if you want to give it a try. |
Thanks @macournoyer. I will try |
I'm testing Rack with Thin 1.2.5 using both HTTP queries with relative URI and absolute URI.
I use map "/" in my Rack builder so it gets any request.
However when I get the value of env["PATH_INFO"] I get an empty string when using absolute URI:
a) Relative URI:
GET /pres-rules/mydoc.xml HTTP/1.1
=> env['PATH_INFO'] = "/pres-rules/mydoc.xml"
b) Absolute URI:
GET http://127.0.0.1:9292/pres-rules/mydoc.xml HTTP/1.1
=> env['PATH_INFO'] = ""
This doesn't occur using webrick.
PS: As per RFC 2616 (HTTP/1.1) a HTTP request allows absolute request uri:
http://tools.ietf.org/html/rfc2616#section-5.1.2
The text was updated successfully, but these errors were encountered: