You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already asked here but maybe this is the better place to ask:
On our internal instance of Mamute I cannot use the website to ask questions. I always get an HTTP error when I go to /ask: 413 FULL head
I also get this error sometimes when going to the homepage.
Other notes:
I have tried clearing cache/cookies for the Mamute domain, but I still get the same error
We use single sign on
I'm on Chrome Version 52.0.2743.116 (64-bit)
Safari works fine
Chrome works fine for others
Incognito in Chrome works fine
From the error message I suspect that my browser is sending too big of a request. I verified and when Safari sends the same request, the cookie is much smaller (less than 1 KB) whereas in Chrome it's almost 2 KB. I verified also that for others that can use Mamute with Chrome their cookie is also much smaller. It seems my cookie has something related to mixpanel in Chrome that doesn't exist in Safari (or for others using Chrome) for some reason.
If I clear all cookies and cache in Chrome it resolves the issue, but only temporarily. A day later the issue came back.
The text was updated successfully, but these errors were encountered:
I already asked here but maybe this is the better place to ask:
On our internal instance of Mamute I cannot use the website to ask questions. I always get an HTTP error when I go to /ask:
413 FULL head
I also get this error sometimes when going to the homepage.
Other notes:
From the error message I suspect that my browser is sending too big of a request. I verified and when Safari sends the same request, the cookie is much smaller (less than 1 KB) whereas in Chrome it's almost 2 KB. I verified also that for others that can use Mamute with Chrome their cookie is also much smaller. It seems my cookie has something related to mixpanel in Chrome that doesn't exist in Safari (or for others using Chrome) for some reason.
If I clear all cookies and cache in Chrome it resolves the issue, but only temporarily. A day later the issue came back.
The text was updated successfully, but these errors were encountered: