3 ms·
we still need your request headers.... the real ones, not the one you think you have
by franze 14y ago
we still need your request headers.... the real ones, not the one you think you have
- philhippus 14y agohttp://i.imgur.com/VhQlE.jpg http://i.imgur.com/VhQlE.jpg The link is a screen cap of the GET request and the displayed error message from Chrome.
- smarx 14y agoThe request looks wrong. Normally you should see a host header of "news.ycombinator.com" and a URL of "/". I.e., it should read "GET / HTTP/1.1".
- sesqu 14y agoYes. This is a "no such file" error.
- philhippus 14y agoThe request is not wrong, the server is wrong. Your answer makes sense though...I had a similar issue with Wordpress mangling redirects because it can't handle absolute URI's after GET. When you change your internet settings on Windows to use a proxy, this is the format to which browsers generate requests. From RFC 2616 5.1.2 Request-URI http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html : 'To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers MUST accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.' My proxy shouldn't have to alter the request, according to the standard.