Http Error 400 Bad Request Asp.net Firefox
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or http error 400. the size of the request headers is too long. chrome posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss http error 400. the size of the request headers is too long. iis Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes http 400 bad request fix a minute: Sign up Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long up vote 18 down vote favorite 3 Some of my users are getting the following error sometimes when
Bad Request - Request Too Long Chrome
they request some of the pages of my site: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long It seems to happen only in Firefox. Deleting the users cookies does help. What I don't understand is the following: I thought that cookies are appended to every request. Why is it that only one or two of my pages show this error and most do never? It is also not dependent on the http error 400. the size of the request headers is too long. mvc server page. If the user requests http://mysite.com/user/Myname he might get the error. If he just changes the capitalization of the URL it works again (like http://mysite.com/user/myname). (I am running IIS which does not care too much about capitalization). For the browser the two URLs are different, for the server they aren't. Any idea what is happening? firefox cookies share|improve this question asked Feb 8 '13 at 18:20 Sparhawk 5231520 add a comment| 4 Answers 4 active oldest votes up vote 22 down vote accepted It seems that there were too many cookies after all. I made sure that there were not so many and it is working now. share|improve this answer edited Jul 30 '13 at 19:48 GatesReign 3161417 answered Feb 24 '13 at 13:09 Sparhawk 5231520 This just happened to me with Ubuntu & Firefox accessing Office365 after the last update. Worked on other computers not my office one. Cleared the Office365 & microsoftonline.com cookies and I am back in! –Phil Lawlor Aug 31 '15 at 12:27 add a comment| up vote 10 down vote Some of our users also ran into this same exception on IE 8 for some our our intranet sites hosted in IIS. The issue turned out to be related to using Kerberos authentication where a user belongs to many active directory groups. We found solutions from the following Microsoft Support Articles: HTTP 400 - Bad Request (Request Header too long)" error in Internet Informatio
thread was archived. Please ask a new question if you need help. I get "HTTP Error 400. The request is badly formed." when trying to access a URL that I have maxrequestbytes accessed previously in the day and works OK with IE. 1 reply 39 have this
Http Error 400. The Size Of The Request Headers Is Too Long. Firefox
problem 12963 views Last reply by cor-el 4 years ago EssJay Posted 11/24/11, 12:02 PM Hi I accessed the site earlier in
Http Error 400. The Size Of The Request Headers Is Too Long. Sharepoint
the day but when I came back to it I got the above message. Tried to access the site in IE and all worked fine. Tried disabling DNS prefetch and clearing out history but to no avail. I http://stackoverflow.com/questions/14778910/bad-request-request-too-long-http-error-400-the-size-of-the-request-headers-i ran a virus scan but with no threat detected. Hi I accessed the site earlier in the day but when I came back to it I got the above message. Tried to access the site in IE and all worked fine. Tried disabling DNS prefetch and clearing out history but to no avail. I ran a virus scan but with no threat detected. Chosen solution That issue can be caused by corrupted cookies. http://kb.mozillazine.org/Cookies Clear https://support.mozilla.org/questions/899452 the cache and the cookies from sites that cause problems. "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now" "Remove Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies" Read this answer in context 7 Question tools Get email updates when anybody replies. when a solution is found. Cancel Subscribe to feed Question details Product Firefox System Details Windows Vista Firefox 8.0 More system details Additional System Details Sites Affected http://www.christopherward.co.uk Installed Plug-ins Google Update RealJukebox Netscape Plugin RealNetworks(tm) RealPlayer Chrome Background Extension Plug-In RealPlayer(tm) HTML5VideoShim Plug-In RealPlayer(tm) LiveConnect-Enabled Plug-In 12.0.1.669 GEPlugin Shockwave Flash 10.3 r183 Google Updater pluginhttp://pack.google.com/ The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site. Adobe PDF Plug-In For Firefox and Netscape 10.1.1 4.0.60831.0 Coupons, Inc. Coupon Printer DLL BBC iPlayer Plugin Application User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0 More Information
Close Tags desktop Firefox 8.0 websites Windows Vista Related The requested URL not found I keep getting an "HTTP ERROR 400" message saying "Problem accessing/service/preauth. Reason: auth token expired. when I go to firefox google start page I receive URL error 404 notice How does built-in Phishing and Malware Protection work? Firefox Health Report - uto occur most often with Google Analytics campaign sources. You should simply try to keep the values in these to alpha characters. I have personally had to fix issues where people https://recalll.co/app/?q=firefox%20-%20ASP.NET%20and%20400%20Bad%20Request%20Error used an apostrophe and an mDash in their query strings. As a result I tell people to just avoid hyphens and apostrophes all together. If you aren't the one including them, you can't be sure they didn't copy a special character the browser can't handle. This forum has a suggestion for clearing the bad cookies on the 400 page so that they can access the site properly. There is already another http error question with the same problem on stackoverflow. You need to make sure that you are not including any special characters before you set the campaign sources etc. Sources that are created dynamically through CMS newsletters etc. can include bad characters if they are not formatted aggressively. We have had trouble with people pasting MSOffice characters into titles and links which break cookies and stop the page from being served. There is http error 400 no solution to the problem other than making sure that you aren't sending bad data to GA and causing cookies to be corrupted. firefox - ASP.NET and 400 Bad Request Error - Stack Overflow View More at http://stackoverflow.com/questions/3139273/asp-net-and-400-bad-re... A 400 Bad Request Error is returned by the Facebook API when one of the parameters isn't valid for the request you're trying to do, you could try manually pasting the requested URL on your browser along with the parameters, it should display the reason of the error as a JSON (On Chrome or Firefox), Something like this for example: { "error": { "type": "OAuthException", "message": "redirect_uri isn't an absolute URI. Check RFC 3986." } From that point on, you can check what's wrong and fix it. c# - (400) Bad Request error running asp.net site at local host - Stac... View More at http://stackoverflow.com/questions/7284552/400-bad-request-error-... This URL seems to be doing user agent string checking. If I adjust my user agent string in Firefox to Python-urllib/2.7, it fails with the Bad Request you are seeing. As you are using urllib, you can adjust the User Agent following this tutorial from urllib.request import FancyURLopener class MyOpener(FancyURLopener): version = 'My new User-Agent' # Set this to a string you want for your user agent myopener