Random errors in backoffice: HTTP 417 The antiforgery token could not be decrypted.
Hi,
We have a backoffice that behaves strange after upgrade from 9->13. We get random http 417 responses on a lot of requests.
Sometimes the backoffice won't load at all and on a next try most background requests will succeed, but not all.
Read other threads about cookie-consent-scripts can mess things up, but on this site there are almost no scripts at all, or other cookies.
Just have UMB-XSRF-TOKEN, UMB-XSRF-V and UMB_UCONTEXT right now.
Grateful for any suggestions how to find out the root cause, cheers :-)
Random errors in backoffice: HTTP 417 The antiforgery token could not be decrypted.
Hi,
We have a backoffice that behaves strange after upgrade from 9->13. We get random http 417 responses on a lot of requests. Sometimes the backoffice won't load at all and on a next try most background requests will succeed, but not all.
Read other threads about cookie-consent-scripts can mess things up, but on this site there are almost no scripts at all, or other cookies. Just have UMB-XSRF-TOKEN, UMB-XSRF-V and UMB_UCONTEXT right now.
Grateful for any suggestions how to find out the root cause, cheers :-)
Our backend server had two instances running. When we changed this to one, it worked fine. So I guess it worked depending on which server was hit.
We are using asp.net data protection with a common key in blobstorage, so I think it should work, but is a problem for later.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.