IE6 client fails to submit on IIS 6 .NET 2.0 page but not on IIS 5.1
am 22.08.2007 00:42:17 von serge
I have a strange problem where a single user is having problems
when he clicks on a SUBMIT button running on our Win 2003 IIS 6
..NET 2.0, but the same user has no problem clicking SUBMIT
button running on our Win XP IIS 5 .NET 2.0.
I have the following details on this user with the problem :
user claims ISP RoadRunner has some sort of a firewall setup on "their
service"
Agent:
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+FunWebPro ducts;+Roadrunner;+SV1;+.NET+CLR+1.1.4322)
Norton Internet Security 10.4.0.13
We've tried disabling Norton Internet Security but that didn't help.
I have the following information from the IIS log files:
In XP's IIS5 logs, User_with_problem registers 2 log entries for the same
aspx page: 302 then 200
In Win2003's IIS6 logs, User_with_problem registers 1 log entry for the same
aspx page: 400 0 64
In Win2003's IIS6 logs, All_other_users register 2 log entries for the same
aspx page: 302 0 0 then 200 0 0
sc-status 400
sc-substatus 0
sc-win32-status 64
400 Bad Request
The request could not be understood by the server due to malformed syntax.
The client SHOULD NOT repeat the request without modifications
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
net helpmsg 64
The specified network name is no longer available
So my question is why this client gets the 400 Bad Request error but
succeeds when
clicking Submit on our XP's IIS 5? What's different on IIS 5 and 6? How come
no other
user is experiencing this problem. Can this be an issue on the client side
caused
by Norton Internet Security or their ISP's extra service of some type of
firewall?
The user's IE shows 1.1.4322, I guess it's .NET 1.1. Should they install
..NET 2.0?
I would appreciate any help.
Thank you
Re: IE6 client fails to submit on IIS 6 .NET 2.0 page but not on IIS 5.1
am 22.08.2007 08:19:38 von David Wang
On Aug 21, 3:42 pm, "serge" wrote:
> I have a strange problem where a single user is having problems
> when he clicks on a SUBMIT button running on our Win 2003 IIS 6
> .NET 2.0, but the same user has no problem clicking SUBMIT
> button running on our Win XP IIS 5 .NET 2.0.
>
> I have the following details on this user with the problem :
>
> user claims ISP RoadRunner has some sort of a firewall setup on "their
> service"
>
> Agent:
> Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+FunWebPro ducts;+Roadru=
nn=ADer;+SV1;+.NET+CLR+1.1.4322)
>
> Norton Internet Security 10.4.0.13
>
> We've tried disabling Norton Internet Security but that didn't help.
>
> I have the following information from the IIS log files:
>
> In XP's IIS5 logs, User_with_problem registers 2 log entries for the same
> aspx page: 302 then 200
>
> In Win2003's IIS6 logs, User_with_problem registers 1 log entry for the s=
ame
> aspx page: 400 0 64
>
> In Win2003's IIS6 logs, All_other_users register 2 log entries for the sa=
me
> aspx page: 302 0 0 then 200 0 0
>
> sc-status 400
>
> sc-substatus 0
>
> sc-win32-status 64
>
> 400 Bad Request
> The request could not be understood by the server due to malformed syntax.
> The client SHOULD NOT repeat the request without modificationshttp://www.=
w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
> net helpmsg 64
>
> The specified network name is no longer available
>
> So my question is why this client gets the 400 Bad Request error but
> succeeds when
>
> clicking Submit on our XP's IIS 5? What's different on IIS 5 and 6? How c=
ome
> no other
>
> user is experiencing this problem. Can this be an issue on the client side
> caused
>
> by Norton Internet Security or their ISP's extra service of some type of
> firewall?
>
> The user's IE shows 1.1.4322, I guess it's .NET 1.1. Should they install
>
> .NET 2.0?
>
> I would appreciate any help.
>
> Thank you
HTTP Status 400 indicates a problem with the request.
If you see the 400 error in HTTPERR log file, then it indicates a
problem with the HTTP compliance of the request itself. This is a
problem with either the client making the request or the networking
devices between the client and server.
If you see the 400 in IIS log files, then it indicates that the
request was rejected in usermode by some application framework.
For .aspx requests, that would be ASP.Net. ASP.Net will fail requests
with 400 for various reasons.
FYI: All your other questions, concerning IIS5/IIS6, Norton Internet
Security, ISP, .Net version on the client, etc -- while interesting to
you, they are not really necessary at this point. Now, I'm not
ignoring them. I'm simply focusing on the information that will make
progress towards resolution. We may find the cause to be one of the
things you mentioned, but it is not worth the time to randomly guess.
Start from the failure and logically work backwards towards the cause.
And make no changes while investigating, on both the client and
server.
http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Ba sics_of_IIS6_Tr=
oubleshooting.aspx
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//