[Openid-specs-fapi] Issue #344: "x-" isn't cool anymore (openid/fapi)

Brian Campbell issues-reply at bitbucket.org
Wed Nov 18 21:33:08 UTC 2020

Previous message (by thread): [Openid-specs-fapi] Issue #343: what is authenticity and integrity of the redirect URI? (openid/fapi)
Next message (by thread): [Openid-specs-fapi] Issue #345: it's okay if a refresh token can be guessed? (openid/fapi)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

New issue 344: "x-" isn't cool anymore
https://bitbucket.org/openid/fapi/issues/344/x-isnt-cool-anymore

Brian Campbell:

Baseline has a few headers like `x-fapi-auth-date` etc., but that x- naming is not what the cool kids are doing these days. See [https://tools.ietf.org/html/rfc6648](https://tools.ietf.org/html/rfc6648)

Previous message (by thread): [Openid-specs-fapi] Issue #343: what is authenticity and integrity of the redirect URI? (openid/fapi)
Next message (by thread): [Openid-specs-fapi] Issue #345: it's okay if a refresh token can be guessed? (openid/fapi)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Openid-specs-fapi mailing list