Is this normal behavior? about nosurf HOT 5 CLOSED

Hi @NCSantos,

The token is only regenerated when the cookie either expires (after 365 days by default), is deleted, or corrupted (i.e. token can not be decoded from the cookie). What you see changing every time is the masked token: 32 byte random key and 32 byte encrypt(key, token) payload. The unencrypted token stays the same for a long time and thus can be reused.

As long as the third party website can not acquire any of the tokens, this seems fine.

See this part in token.go and this part in handler.go.

Hope that answers your question.

from nosurf.

Hi @justinas ,

When calling the GET also regenerate the token, e.g.:
Call GET, call POST with token from GET, call GET again, call POST with token from first GET is not valid.

from nosurf.

I think you are misunderstanding what actually happens. The token in the cookie is unmasked, you can check it: it should not change whether you GET or POST as many times as you'd like. This is the value we care about. The thing that changes is the token for the forms (masked). To be more exact, this token's masking key is regenerated on every request, but the same token is masked every time.

Nosurf does not aim to prevent guarantees from double-submit of requests.

from nosurf.

I am using curl to do the requests and was not correctly sending and saving the cookies.
Thanks for your help.

from nosurf.

No problem, please re-open the issue if you encounter such troubles again.

from nosurf.