Bad Request answer

External Since: Feb 11, 2008 Posts: 2

For a project I have to use an IIS server to control a Dynamic DNS system.
The client, a VPN router, has to use the DynDNS update/registration protocol.

With software clients and other hardware, the updating mechanism works just
fine. However, with the VPN router has problems.

In the URL request message, the content length is set to 0, which will end
the HTTP GET request, which results in a "400 - Bad Reuqest" from the IIS
server.

My question would be:
"Is it possible to handle the request, eventhough IIS says it's a bad
request?"

I've tried custom error pages, but these didn't have any effect. And when I
disabled the website, the result was the same. So I'm thinking that it goes
wrong before the domain/binding selection. Is it possible to handle an error
on that place?

I hope someone can help me. If someone needs meer information, please let me
know.

External Since: Aug 23, 2003 Posts: 3041

Hi,

I am going to assume that you are using IIS 6.0. In that case, parsing of
the HTTP request is initially done by http.sys, which returns 400 Bad
Request if the incoming request is malformed.

The solution here is to fix the client, rather than try to "work around" or
somehow intepret what the client should have expressed using a properly
formed HTTP request.

Cheers
Ken

--
My IIS blog: http://adopenstatic.com/blog

"G.J. Admiraal" <GJAdmiraal.TakeThisOut@discussions.microsoft.com> wrote in message
news:AB46B786-678B-44C2-B7D8-54AFB65F724C@microsoft.com...
> For a project I have to use an IIS server to control a Dynamic DNS system.
> The client, a VPN router, has to use the DynDNS update/registration
> protocol.
>
> With software clients and other hardware, the updating mechanism works
> just
> fine. However, with the VPN router has problems.
>
> In the URL request message, the content length is set to 0, which will end
> the HTTP GET request, which results in a "400 - Bad Reuqest" from the IIS
> server.
>
> My question would be:
> "Is it possible to handle the request, eventhough IIS says it's a bad
> request?"
>
> I've tried custom error pages, but these didn't have any effect. And when
> I
> disabled the website, the result was the same. So I'm thinking that it
> goes
> wrong before the domain/binding selection. Is it possible to handle an
> error
> on that place?
>
> I hope someone can help me. If someone needs meer information, please let
> me
> know.