Bad Request (Header Too Long)

[seoqueen]

Bad Request (Header Too Long) does this look familiar? The only thing that was changed was adding a scrollbar code and everytime I hit Save I get that message. If I hit refresh everything goes back to normal.

Has anyone seen this before and can you tell me how you fixed the issue?

Thanks,

seoqueen

[jmestep]

What build are you running? There was an issue that cropped up in various places that was fixed with a patch on one of the upgrades in the global.asax file:
protected void Session_OnStart()
{
//SAVE THE REFERRER FOR USE BY THE ORDER MODULE
if (Request.UrlReferrer != null) Session["SessionReferrerUrl"] = StringHelper.Truncate(Request.UrlReferrer.ToString(), 255);
}

[seoqueen]

PLATFORM: ASP.NET
VERSION: 7.0
BUILD: 10125

Does this help. What would be my next step to fix this error. Upon further testing this only occurs when I use IE7, everything works fine in FireFox.

Thanks,

seoqueen

[afm]

It is probably caused by a long cookie, or a new cookie that put you over the limit. I think the limit is 16KB in IIS 6 and earlier. All browsers keep a separate list of cookies for each site. My guess is that the IE7 list is longer than the FF list, so that is why you only see the error with IE7.

A possible quick fix is to delete all the cookies in IE7 for the site (or all cookies). There may have been an old one that is creating the problem. If that does not fix it, then use something like Fiddler (http://www.fiddlertool.com) to inspect the request header. The culprit(s) should be obvious. Then rewrite your pages to eliminate or mitigate the culprit(s).

[seoqueen]

afm, thank you so much!!! that did the trick.

Not sure what could have put me over the limit but you're sooo smart!!!!

Thanks,

seoqueen