does anyone have experience dealing with http 413s on heroku? every request sees one, and i have no idea why, and no way to debug, and neither does support
Show this thread
-
-
This has happened to me on certain domains in the past when something the site was doing (probably tracking) caused the cookie to get large enough for the site to reject all requests. It's likely being caused by the HTTP parsing library as a safety feature.
-
Incognito mode would be a decent way to check
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.