Can't post/navigate forums in Chrome

[A790]

I receive the following error message in Chrome:

400 Bad request

Your browser sent an invalid request.

Chrome version: 36.0.1985.143 m

[Mitsu3000gt]

No issues for me with Chrome desktop or mobile.

Version 36.0.1985.143 m

I know that isn't very helpful, but maybe something else is up?

[rage2]

Clear your cookies. Chrome somehow corrupts cookies and does that once in a while. I'm not sure if you can specifically clear cookies for beyond, or if you have to clear all.

[A790]

Just updated to 37.0.2062.103 m. Same issues.

[spike98]

Version 37.0.2062.103 m

Have never had a problem browsing Beyond with Chrome.

[D'z Nutz]

http://forums.beyond.ca/st/363022/400-bad-request-error/

http://forums.beyond.ca/st/367847/400-bad-request/

http://forums.beyond.ca/st/375889/beyond-stopped-working-on-my-mobile/

http://forums.beyond.ca/st/371819/404-bad-request-from-mobile-device/

[firebane]

When there becomes too many of these ASPSESSIONIDs you will get that 404 error.

Just go in and remove all the ASPSESSIONIDs you have for the site and refresh and it'll correct itself.

[benyl]

Clear cookie and browsing data. Happens on my iPad all the time.

[firebane]

Originally posted by benyl
Clear cookie and browsing data. Happens on my iPad all the time.

Clearing cookies for a website is very extreme.

I would recommend to clear the cookie for the website that is giving you grief but if you have the option of removing portions of a cookie then just remove the ASPSESSIONIDs and you'll retain your login and such.

[benyl]

Chrome on iPad doesn't let you do that. all or nothing.

[rage2]

Thanks for the cookies image. I've started a case with our caching provider to nail down the issue. I've never been able to duplicate it, so that helps a lot.

[A790]

:)

Cleared cache/etc. and we're good to go.

[rage2]

I've also made a change on our servers to disable sessions as we don't use them, which should in theory get rid of the ASPSESSIONID* cookies that are causing the issue. In theory, the ASPSESSIONID cookies aren't persistent, so they should just disappear when you close the browser. I'm not sure why Chrome and some mobile browsers decides that it should keep the session cookies. We have a pool of 4 web servers to serve requests, so there should be no more than 4 of those cookies at any time depending on how your session gets load balanced.

[firebane]

Originally posted by rage2
I've also made a change on our servers to disable sessions as we don't use them, which should in theory get rid of the ASPSESSIONID* cookies that are causing the issue. In theory, the ASPSESSIONID cookies aren't persistent, so they should just disappear when you close the browser. I'm not sure why Chrome and some mobile browsers decides that it should keep the session cookies. We have a pool of 4 web servers to serve requests, so there should be no more than 4 of those cookies at any time depending on how your session gets load balanced.

Yeah I noticed it happens in both Firefox and Chrome so I would assume it happens in a lot of other browsers.

I don't close my browser very often so that could also cause the issue to become more persistent.