Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

When trying to log into a website recently I've ran into an error - Bad Request - Size of a request header field exceeds server limit: Cookie. Immediately I opened the developer console and skipped over to the storage tab (in Safari). It showed me a thriving population of cookies living in my browser cache for the domain that website was running on.
badreq_1.png


The number of cookies was out of control and one was fairly large. Overall the total size of the cookies was well over 4kb. This doesn't seem like much, but RFC6265 only provisions for numbers in this area.
badreq_2.png


So I deleted the largest cookie and then was able to log in. Easy.
badreq_3.png


This kind of error bothers me though because it could have been very easily prevented. There are multiple parties that can be blamed in this case - the application developer, the server administrator, the web browser developer. Who is really to blame though? I say the majority responsibility is with the application developer but other parties can also help to improve user experience.

At least there is a way forward by manually deleting cookies! 🍪



-i

Skip down to comments...
Hope you found this post useful...

...so please read on! I love writing articles that provide beneficial information, tips and examples to my readers. All information on my blog is provided free of charge and I encourage you to share it as you wish. There is a small favour I ask in return however - engage in comments below, provide feedback, and if you see mistakes let me know.

If you want to show additional support and help me pay for web hosting and domain name registration, donations, no matter how small, are always welcome!

Use of any information contained in this blog post/article is subject to this disclaimer.
 
comments powered by Disqus
Other posts you may like...