Mystical 411 error

Strange error keeping my site from loading for some users..

[anxvariety]

Suddenly 2 days ago I noticed some of my tracking statistics dropping dramatically.. That is 3rd party ad services impression counts.

I looked through my logs and found that about 40% of my users were receiving HTTP 411 - Content Length Required on my home page 'default.asp'.

After looking a little closer at the logs I now notice that only Windows 98 users running IE 5.5 receive this error.

I tried renaming main page to 'index.htm' 'default.htm' etc.. These users still receive the error.

My hosting company is completely stumped by this.. I haven't found any information out there that addresses this issue.

Anyone have a clue what might be causing this or a possible solution?

Below is a sample of what a succesful request from non-98 users looks like, as well as a unsucccesful request from Windows 98 user.

Non-Windows 98:

2003-08-19 01:25:28 W3SVC280 /default.asp - 200 0 458 156 Mozilla/4.0+compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322) ASPSESSIONIDAADASQAC=JMFEKGAAPOKAOHEAHKMGFLMP -

Windows 98:

2003-08-19 01:17:10 W3SVC280 / - 200 0 193 203 Mozilla/4.0+(compatible;+MSIE+5.5;+Windows+98) - -
2003-08-19 01:17:10 W3SVC280 / - 411 214 70 16 - - -

[closed]

Windows Server or ASP problem, maybe?

You'll probably be helped faster if you posted this in the "Microsoft Related - .NET and ASP" forum.

[plumsauce]

Best is to do a full network trace on this
from the client end. I say the client end,
because it is it easier to isolate the
traffic in the dump that way.

Possible cause is that the browser is
pushing some content towards the server
without a content-length header.

+++

[wgp1954]

I noticed the same problem on one of my servers. I was geeting tons of 411 errors as you mentioned. I noticed the error was being created because I was getting requests that included the servers IP address with no page reference.(ie [xxx.xxx.xxx.xxx)...] I got rid of these pesky hits by removing the "All Unassigned" entry in the Multiple Identity option for the Default web site. In doing this the server will not try to resolve any entries not specifically listed.