Re: HTTP 400 - Bad Request
From: Dave Munday (thehappymundays_at_hotmail.com)
Date: 09/19/04
- Next message: Nim: "Re: Internet services manager"
- Previous message: Ken Schaefer: "Re: Canonical Name record on IIS"
- In reply to: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Next in thread: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Reply: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 19 Sep 2004 15:47:39 +0200
David
many thanks for your support. I shall start tomorrow on trying to gt to the
bottom of this.
Can you advise on the taking of the network trace
thanks
Dave
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:O69LU$SnEHA.3756@TK2MSFTNGP11.phx.gbl...
> Umm, none of those settings have ANYTHING to do with a 400 Bad Request.
>
> 400 Bad Request indicates something wrong with the request when it is
> parsed, and IIS never bothered to execute it. All the areas that you
pointed
> out requires IIS to execute the request (to even care about
authentication,
> execute permissions, or file ACLs) -- thus they have to be completely
> irrelevant by definition.
>
>
> 400 bad request typically indicate a client-side issue since it is the one
> that is sending the bad request. The server is simply informing the user
of
> that fact by returning a 400 error.
>
> 400 Bad Requests are best troubleshoot by taking a network trace of the
> "bad" request and see what is wrong with it (post the capture to this
> newsgroup if you cannot read HTTP). This requires the cooperation of
> whoever is getting the "400 Bad Request" -- because everyone else will be
> perfectly unaffected.
>
> As for the "Page not found" errors -- those require you to turn off the
> browser's "Show Friendly HTTP Errors" option and retrieving the actual
error
> code. Please post the actual error code and we can proceed further.
>
>
> You have to do these basic things to troubleshoot -- randomly changing
> settings will not help and can harm.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Craig" <anonymous@discussions.microsoft.com> wrote in message
> news:35e401c49d16$0411e720$a601280a@phx.gbl...
> Hello Dave,
>
> I know this issue. Please check your IIS website name
> settings in the following areas.
>
> - IIS Authenication
> - IIS Scripts and Executibles
> - Windows System Folder Permissions
>
> If you would like to correspond further, I have created a
> temporary email address you can contact me at:
>
> DAVE3-CONTACT-CRAIG@GNIS.NET
>
> Sincerely,
>
> Craig
>
> >-----Original Message-----
> >Hello folks, I may not be in the right place so
> apologies if not
> >
> >I have a small IIS 6.0 site on my Windows 2000 server
> that is used to
> >require user acceptance of school rules prior to
> accessing the Internet.
> >This works fine and 95% of web browsing is okay. However
> we often get the
> >HTTP 400 - Bad Request message and pages not found. When
> I come home the
> >same page displays as expected.
> >
> >Can anybody please point me in the right direction for
> addressing this
> >
> >Thanks
> >
> >Dave
> >
> >
> >.
> >
>
>
- Next message: Nim: "Re: Internet services manager"
- Previous message: Ken Schaefer: "Re: Canonical Name record on IIS"
- In reply to: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Next in thread: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Reply: David Wang [Msft]: "Re: HTTP 400 - Bad Request"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|