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
The current logic of SameOriginCsrfTokenManager is that the hostname must be an exact match and this not configurable. Perhaps a whitelist of allowed domains, or just an option to allow subdomain matches of the same TLD would be useful.
Example
Requests from https://foo.steam250.com should also be allowed to https://bar.foo.steam250.com.
The text was updated successfully, but these errors were encountered:
Bilge
changed the title
[CSRF] Allow subdomains to match origin/refer headers
[CSRF] Allow subdomains to match origin/referer headers
Jun 5, 2025
Uh oh!
There was an error while loading. Please reload this page.
Description
The current logic of
SameOriginCsrfTokenManager
is that the hostname must be an exact match and this not configurable. Perhaps a whitelist of allowed domains, or just an option to allow subdomain matches of the same TLD would be useful.Example
Requests from
https://foo.steam250.com
should also be allowed tohttps://bar.foo.steam250.com
.The text was updated successfully, but these errors were encountered: