• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1684
  • Last Modified:

Invalid Request (Bad Verb)

I am running an ASP.NET 2.0 application on IIS 6, Windows Server 2003 Web Edition. By no pattern that I can discern, about one in 300-500 individual requests results in the IIS error "Invalid Request (Bad Verb)".

I cannot figure out what is causing this error - my application does not manipulate the HTTP headers, so it could not be a programming bug. Also, on a separate physical server, another copy of the same site is running that is, for all practical purposes, the same version of the code, and it has not once encountered this error. As far as I can determine, the Web Site configurations of the two are identical. This behavior has persisted across over 100 builds and code changes without any discernable improvement or degredation.

Any help getting me even pointed in the right direction would be most appreciated.
0
sexyrexy
Asked:
sexyrexy
  • 2
  • 2
1 Solution
 
dnojcdCommented:
you are gettign this error since the client is sending an invalid request.prior to IIS 6 the web server used to accept invalid requests but after the iis http.sys does not accept them for security reasons.most porbably the other server running the same code is not IIS 6.
so surely this is an apllication bug :-)
If you can check the requests being send form the browser using some software you may be able to find what the browser is trying to send to the web server.
0
 
sexyrexyAuthor Commented:
Both servers are very nearly identical, hardware and software-wise. Windows Server 2003 Web Edition with IIS 6. However, what is this about "http.sys"? Is this something that could inadvertently be different between the two systems that would affect this?
0
 
dnojcdCommented:
oops both are 2003 servers . i was thinking the other way .http.sys  will be there only for iis 6 servers. can you download IIS resource tools and check with wfetch from the client side
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/c7d368f0-f175-4d58-b7a8-977e1d67bd07.mspx?mfr=true
0
 
sexyrexyAuthor Commented:
dnojcd's comments were knowledgeable but ultimately incorrect - the problem was coming from the proxy server used by the group that was testing the website.
0
 
GranModCommented:
PAQed with points refunded (250)

GranMod
Community Support Moderator
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now