Header Too Long Error
Contents |
360 games PC games bad request - request too long chrome Windows games Windows phone games Entertainment All Entertainment
Bad Request - Request Too Long Google Chrome
Movies & TV Music Business & Education Business Students & educators
How To Fix Error 400
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
400 Bad Request Error
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All 400 bad request request header or cookie too large Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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 400 bad request chrome posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss 400 bad request nginx 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 400 bad request instagram takes a minute: Sign up Size of the request headers is too long up vote 0 down vote favorite I'm currently working on an ASP.NET MVC website and it works fine. But I have a problem that I don't understand https://support.microsoft.com/en-us/kb/2020943 at all... When I launch my website on Visual Studio with Chrome for example no problem, but when I stop it and try to launch an other test with Firefox for example, my url is growing and then I get this error : HTTP 400. The size of the request headers is too long. Can someone explain me why this is happening ? Is it something with my code or does it come from IIS express or anything else ? Thanks http://stackoverflow.com/questions/37112367/size-of-the-request-headers-is-too-long in advance asp.net share|improve this question asked May 9 at 9:39 MrPixel6 6710 1 Possible duplicate of Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long –CodeCaster May 9 at 9:41 May you show us http request this return the response? –Mediator May 9 at 9:41 Use your browser's debugging tools or a proxy like Fiddler to see what is actually going on. From there, you can do more research. With the given information, we can't do anything but guess. See for example Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. –CodeCaster May 9 at 9:42 seems like same issue Link –Rahul R G May 9 at 9:46 Thank you guys but I already saw this post but it's only a problem about having too much cookies ? Nothing else can cause that ? –MrPixel6 May 9 at 10:11 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote Check the MSDN: Cause This issue may occur when the user is a member of many Active Directory user groups. When a user is a member of a large number of active directory groups the Kerberos authentication token for the user increases in size. The HTTP request that the user sends to the IIS server contains the Kerberos t
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
February 26, 2014February 15, 2016 as article KB0016178
Issue: Logging into web sites using Google Chrome, you may receive an error message like the one listed below: "Bad Request - Request Too Long""HTTP Error 400. The size of the request headers is too long." This is for Duke shibboleth sites. Environment: Google Chrome Cause: invalid cookie from previously visiting a Duke shibboleth protected website Resolution: Logging into web sites using Google Chrome, you may receive an error message like the one listed below: "Bad Request - Request Too Long""HTTP Error 400. The size of the request headers is too long." This is for Duke shibboleth sites. Quick Access Solution : 1) You can use a incognito browser in Chrome, you will be able to access mail.duke.edu. (Click here for help with opening a incognito browser) Long Term Solution: 1) Clear cookies and cache in Google Chrome, and if this doesn't work proceed to step two. 2) Click on the "Setting button" in the top right hand corner. 3) Click on "Setting" 4) Click on " Show Advanced Setting" 5) Under Privacy click on " Clear browsing data" 6) Next, click on "All Cookies and Site Data" 7) Next to "obliterate the following items from," please drop the box down to "the beginning of time" 8) Check-mark the boxes for "Cookies and other site and plugin data" and "Cached images and files" 9) Restart Chrome 10) Go to web site - login with netid and netid password to try it again This entry was posted in Messaging and Calendaring, Office 365 and tagged configure o365 office365 office 365 outlook 2013 exchange, Google Chrome, HTTP Error 400, mail.duke.edu. Bookmark the permalink. 0 people found this article useful This article was helpful This article was helpful 0 people found this article useful Post navigation