setup.exe and HTTP Host header
Abraham Backus
abraham@backus.com
Mon Dec 2 23:26:00 GMT 2002
I've discovered that in some cases I'm not getting the response that I
expect from the HTTP request that setup.exe issues. I believe my particular
case is probably a misconfiguration of the Apache server that hosts my
website, but in any case I think it might make the setup.exe user experience
a little better if, when generating the HTTP "Host:" header, that it
shouldn't include the (optional) port parameter if it is the default port of
80.
Here's an example of my problem...
This is pretty much what setup.exe is sending:
> telnet abraham.backus.com 80
GET /setup.ini HTTP/1.0
Host: abraham.backus.com:80
...spits back some default stuff from netidentity.com, the company that
hosts my site...
This is what works with the way the web server is configured:
> telnet abraham.backus.com 80
GET /setup.ini HTTP/1.0
Host: abraham.backus.com
...spits back the content of my setup.ini...
I've attached a patch for nio-http.cc that should help setup.exe work
through this problem. I haven't been able to unit test this fix as I can't
seem to get setup.exe to build. This sounds familiar so I will of course
search the archives for why I can't get it to build :)
thanks!
-Abe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cygwin-setup.patch
Type: application/octet-stream
Size: 874 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20021202/f2e61f55/attachment.obj>
More information about the Cygwin-apps
mailing list