Re: BigIP / ASP.NET Webservice Bad Request
From: Egbert Nierop \(MVP for IIS\) (egbert_nierop_at_nospam.invalid)
Date: 02/18/05
- Next message: Egbert Nierop \(MVP for IIS\): "Re: Unable to start debugging on the web server."
- Previous message: Steve Maddison: "Re: Granting IIS rights to regular user"
- In reply to: Johan Burman: "BigIP / ASP.NET Webservice Bad Request"
- Next in thread: Johan Burman: "Re: BigIP / ASP.NET Webservice Bad Request"
- Reply: Johan Burman: "Re: BigIP / ASP.NET Webservice Bad Request"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Feb 2005 11:19:04 +0100
"Johan Burman" <johan.burman@sorry.cant.tell.com> wrote in message
news:eYkoo8YFFHA.2176@TK2MSFTNGP15.phx.gbl...
> Hi all
>
> I got a bit of an odd problem at hand;
>
>
> Background:
>
> My application consists of a website ("consumer layer") that frequently
> communicates with a set of webservices ("service layer"), both based on
> ASP.Net. For the time being, the consumer layer and the service layer is
> located on the same IIS (running on a Windows Server 2003).
>
>
> Problem:
>
> Recently, I made an attempt to put this application behind a BigIP box.
> When doing this I discovered that several of the webservice requests
> resulted in a 401 error. If BigIP was removed, everything went back to
> normal.
In this case, BigIP is the hardware and source to get consult from.
>
> Extra info:
>
> I did a few dumps of the network traffic between the BigIP box and the
> webserver and found that the real response sent from the webserver was
> "HTTP/1.1 400 Bad Request", and this only happened with webservices that
> had datasets as input parameters. These requests had content lengths in
> the region of 40 kB.
> After some googling I found that windows 2003 server has a default size
> limit on http requests set at 16 kb, and breaking this limit will result
You mean on URL sizes...
> in a bad request... However, if this was the case, how come it works when
> not running through the BigIP? Running the consumer and service layer on
> separate servers also works just fine. The "Bad request" only occurs when
> BigIP is routing the traffic.
Webservices, by default use a POST verb, not a GET verb.
Bad Request is in fact that IIS says that the client sends an incomplete or
invalid request. In your case, I suspect that the BigIP router, does not
buffer or pass-through the whole request and cuts off data which results in
the bad request.
Please consult your bigIP docs.
ps: It would help, to install netmon.exe (this is a network sniffer from the
Windows 2000 server CD!) and install the network monitor driver in your
network applet. Filter on HTTP and you'll see exactly what IIS receives from
the external clients.
> Also, the application uses windows authentication...
>
> Any help is appreciated!
>
> //JohanB
- Next message: Egbert Nierop \(MVP for IIS\): "Re: Unable to start debugging on the web server."
- Previous message: Steve Maddison: "Re: Granting IIS rights to regular user"
- In reply to: Johan Burman: "BigIP / ASP.NET Webservice Bad Request"
- Next in thread: Johan Burman: "Re: BigIP / ASP.NET Webservice Bad Request"
- Reply: Johan Burman: "Re: BigIP / ASP.NET Webservice Bad Request"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
