Ok so my thing signed me out while I was writing a fourm post and then when i tried logging back in it gave me an error 403 message and then when I refreshed the tab name was “403 Forbidden” and it said debug = false WHAT IS GOING ON HERE it works fine now

bump


because this is important

Might be a google bug.

Could you post your browser/operating system? It automatically gets added to your post, but either you removed it or it didn't work.

Elijah999999 wrote:

Could you post your browser/operating system? It automatically gets added to your post, but either you removed it or it didn't work.

It doesn’t do that on my mobile device, so maybe he’s on mobile?

nightbkid wrote:

Elijah999999 wrote:

Could you post your browser/operating system? It automatically gets added to your post, but either you removed it or it didn't work.

It doesn’t do that on my mobile device, so maybe he’s on mobile?

no i am not on mobile. My browser / operating system: Windows NT 10.0, Chrome 131.0.0.0, No Flash version detected

bump bump bump this article 2 the top of the fourms plz

there's a topic about the signing out bug here: https://scratch.mit.edu/discuss/topic/799953/

cloverfly wrote:

there's a topic about the signing out bug here: https://scratch.mit.edu/discuss/topic/799953/

no its more then that

CoderMCProX wrote:

cloverfly wrote:

there's a topic about the signing out bug here: https://scratch.mit.edu/discuss/topic/799953/

no its more then that

403 forbidden

My browser / operating system: Windows NT 10.0, Chrome 131.0.0.0, No Flash version detected

ok i couldnt find the other version of this but when submitting a fourm post my thing signed me out after signing bak in it said error 403 and when i refreshed tab name changed to 403 Forbidden and it showed sus stuff it works fine now tho

bump

https://en.scratch-wiki.info/w/images/403_Request_Aborted.png

if <not at top> then
bump
end

bump

you're not alone (yesterday when I was submitting a reply my scratch BRICKED and said the scratch server is Scratch'ing it's head

nightbkid wrote:

CoderMCProX wrote:

cloverfly wrote:

there's a topic about the signing out bug here: https://scratch.mit.edu/discuss/topic/799953/

no its more then that

403 forbidden

yes

bump

define 403 Forbidden

I got this yesterday, and reloading seemed to fix it.

This typically happens when a malformed CSRF token gets sent to the server.

Bump

BigNate469 wrote:

I got this yesterday, and reloading seemed to fix it.

This typically happens when a malformed CSRF token gets sent to the server.

I know a lot about computers, but I don't really speak that kind of computer language can you explain that to me in other terms?

CoderMCProX wrote:

BigNate469 wrote:

I got this yesterday, and reloading seemed to fix it.

This typically happens when a malformed CSRF token gets sent to the server.

I know a lot about computers, but I don't really speak that kind of computer language can you explain that to me in other terms?

a CSRF Token is a special token that verifies something. You seem to be getting this because your browsing session doesn't match with the one it is sending. However, it is showing 403 forbidden instead, therefore implying that it might be sending another user's session and acting as if you are trying to access their session, so it shows 403 to stop you from doing it.

PIXEL_BY_PIXEL_ERROR wrote:

CoderMCProX wrote:

BigNate469 wrote:

I got this yesterday, and reloading seemed to fix it.

This typically happens when a malformed CSRF token gets sent to the server.

I know a lot about computers, but I don't really speak that kind of computer language can you explain that to me in other terms?

a CSRF Token is a special token that verifies something. You seem to be getting this because your browsing session doesn't match with the one it is sending. However, it is showing 403 forbidden instead, therefore implying that it might be sending another user's session and acting as if you are trying to access their session, so it shows 403 to stop you from doing it.

I am not trying to access their session, I'm just trying to log back in. does ST know about this?

CoderMCProX wrote:

PIXEL_BY_PIXEL_ERROR wrote:

CoderMCProX wrote:

BigNate469 wrote:

I got this yesterday, and reloading seemed to fix it.

This typically happens when a malformed CSRF token gets sent to the server.

I know a lot about computers, but I don't really speak that kind of computer language can you explain that to me in other terms?

a CSRF Token is a special token that verifies something. You seem to be getting this because your browsing session doesn't match with the one it is sending. However, it is showing 403 forbidden instead, therefore implying that it might be sending another user's session and acting as if you are trying to access their session, so it shows 403 to stop you from doing it.

I am not trying to access their session, I'm just trying to log back in.

I know you aren't, but the computer accedently got sent the wrong session, making that screen pop up.