Allow a bad get request - Windows 2003 server

Hi, I have an old program that can not be updated. The program worked
on WIndows 2000, but has stopped working windows 2003. The request now
goes into the httperr.log file (Timer_HeaderWait error), and does not
get processed by IIS6.

Below is a trace of the GET request. It is incorrect since the
"http://www.1234.com" is part of the GET request, where it is not
needed, and this is why I think Windows 2003 is killing it.

GET http://www.1234.com/asp/update.asp?id=FFFFFFFF HTTP/1.1
Host: www.1234.com:80
User-Agent: 1234Dgtl
CONTENT-TYPE: text/xml; charset="utf-8"


Does anyone know of a registry work around to allow this request to
work on Windows 2003 server?


Thank you,
David

Are you using Host Headers to serve multiple sites?

The HeaderWait error is what's got me thinking that may be involved. I'm
also thinking that the functionality of the IIS Lockdown tool was built into
IIS 6, but don't know how to modify it. If you haven't cross posted this to
an IIS group, it might be a good idea to do so.

It would also be great to see the response packet showing the error and a
successful request and response from the old 2000 server if it's still
running.

--

Mike Shepperd
Sunfire Solutions LLC
Seattle, WA

[This posting is provided AS-IS, with no warranties and confers no rights]


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi, I have an old program that can not be updated. The program worked
> on WIndows 2000, but has stopped working windows 2003. The request now
> goes into the httperr.log file (Timer_HeaderWait error), and does not
> get processed by IIS6.
>
> Below is a trace of the GET request. It is incorrect since the
> "http://www.1234.com" is part of the GET request, where it is not
> needed, and this is why I think Windows 2003 is killing it.
>
> GET http://www.1234.com/asp/update.asp?id=FFFFFFFF HTTP/1.1
> Host: www.1234.com:80
> User-Agent: 1234Dgtl
> CONTENT-TYPE: text/xml; charset="utf-8"
>
>
> Does anyone know of a registry work around to allow this request to
> work on Windows 2003 server?
>
>
> Thank you,
> David
>

Hi Mike,

No, I am not using host headers. Once a request reaches the
httperr.log area it is a black hole with no response. I have crossed
posted to an IIS group. Thanks for you help.


Mike Shepperd wrote:
> Are you using Host Headers to serve multiple sites?
>
> The HeaderWait error is what's got me thinking that may be involved. I'm
> also thinking that the functionality of the IIS Lockdown tool was built into
> IIS 6, but don't know how to modify it. If you haven't cross posted this to
> an IIS group, it might be a good idea to do so.
>
> It would also be great to see the response packet showing the error and a
> successful request and response from the old 2000 server if it's still
> running.
>
> --
>
> Mike Shepperd
> Sunfire Solutions LLC
> Seattle, WA
>
> [This posting is provided AS-IS, with no warranties and confers no rights]
>
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > Hi, I have an old program that can not be updated. The program worked
> > on WIndows 2000, but has stopped working windows 2003. The request now
> > goes into the httperr.log file (Timer_HeaderWait error), and does not
> > get processed by IIS6.
> >
> > Below is a trace of the GET request. It is incorrect since the
> > "http://www.1234.com" is part of the GET request, where it is not
> > needed, and this is why I think Windows 2003 is killing it.
> >
> > GET http://www.1234.com/asp/update.asp?id=FFFFFFFF HTTP/1.1
> > Host: www.1234.com:80
> > User-Agent: 1234Dgtl
> > CONTENT-TYPE: text/xml; charset="utf-8"
> >
> >
> > Does anyone know of a registry work around to allow this request to
> > work on Windows 2003 server?
> >
> >
> > Thank you,
> > David
> >