Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

I'm having an issue with csrf token on a fresh login flow when sending the browser request to `/login?flow={flow_id}`:
```the request was rejected to protect you from Cross-Site-Request-Forgery```
I see that the request does have a csrf token cookie called `csrf_token_88992335412a638969f212b4e92ba3455bdcd1dc83c43c56abf3dfe42317f1da`? why does it happen even on a basic get request to load the login form?

I upgraded to the latest `v1.0.0`, but it still happens

it seems like issues started appearing when we were forced to switch our cluster setup to HTTP2 (H2C internally).

but the requests to oathkeeper/kratos go via http1.1. could it have something to do with `X-Forwarded-*` headers?