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 have noticed that hooman's hook that sets the referer for the request sets it as the url you are requesting too. This is okay behaviour for some sites that don't vigourously check these things but for example I would get a 403 response for a post request that also had a unique query param token in it and after looking at the response I saw that it is because the referer is set to the current request URL.
This is the only instance it has occured to me but is likely causing some other peoples 403 responses and wanted to flag it incase you choose to change the behaviour or make other people aware
The text was updated successfully, but these errors were encountered:
I have noticed that hooman's hook that sets the referer for the request sets it as the url you are requesting too. This is okay behaviour for some sites that don't vigourously check these things but for example I would get a 403 response for a post request that also had a unique query param token in it and after looking at the response I saw that it is because the referer is set to the current request URL.
This is the only instance it has occured to me but is likely causing some other peoples 403 responses and wanted to flag it incase you choose to change the behaviour or make other people aware
The text was updated successfully, but these errors were encountered: