Can you check the httperr1.log file and post the entries from it that show
the HTTP 400 errors. That log should show more about the request itself.
The below article may also help if you are running into one of the problems
mentioned in it.
828726 FIX: Http.sys Rejects Requests That Contain Separator Characters
<a style='text-decoration: underline;' href="http://support.microsoft.com/?id=828726" target="_blank">http://support.microsoft.com/?id=828726</a>
Thanks,
Kyle Terns, MCSD [MSFT]
***********************
>>Please do not send email directly to this alias. This is an online
account name for newsgroup participation only.<<
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
© 2003 Microsoft Corporation. All rights reserved.
***********************
--------------------
| Thread-Topic: Bad Request (Invalid Verb)
| thread-index: AcPxkXza5+DuBlWJSp+o1QbX64rlcw==
| X-Tomcat-NG: microsoft.public.inetserver.iis
| From: "=?Utf-8?B?QWpvaG5zb24=?=" <anonymous DeleteThis @discussions.microsoft.com>
| Subject: Bad Request (Invalid Verb)
| Date: Thu, 12 Feb 2004 09:56:06 -0800
| Lines: 7
| Message-ID: <43181EEB-533B-4AA4-ABD5-ACE9C9B4CED4 DeleteThis @microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.inetserver.iis
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.inetserver.iis:294600
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| We have an ASP .NET application that "lives" in its own sub folder
beneath our main site. Users access it via a link we have created inside
of the OWA interface, but the application is not integrated with OWA. The
OWA and the link to our application are all SSL based. The problem we are
experiencing is that when we first make a request to our application we get
an error "Bad Request (Invalid Verb)" (code 400). The log files indicate a
request with an HTTP/0.0 protocol on the failed request. If we click the
link again all or most of the content will succesfully load. We can then
switch between OWA and the app with only random (paritial) failures on our
application loading. The failures include, one of the frames of our app
giving a 400 (we have three parts to our apps frame) or some of the images
randomly not loading.
We are on Exchange 2003 Enterprise on Windows 2003 Server Enterprise
Our direcory structure is the default C:\Inetpub\wwwroot and our app is in
sub folder under wwwroot. Our app is a virtual directory under the wwwroot
folder. Other then the above mentioned, once inside our app we have
performance or usage issues, it is only the initial connection that is
causing us problems.
If there is any additional information that can can/be provided to help
diagnose this issue please let me know.
|<!-- ~MESSAGE_AFTER~ -->
FAQ
Profile
Private Messages
Log in
