On Fri, May 01, 2020 at 09:32:27AM +1000, Mark Nottingham wrote:
> (a) (b) Appendix A already talks about it some:
>
> """
>Why aren't per-directory well-known locations defined?
> Allowing every URI path segment to have a well-known location
> (e.g., "/images/.well-known/") would
Hi Nico.
(a) (b) Appendix A already talks about it some:
"""
Why aren't per-directory well-known locations defined?
Allowing every URI path segment to have a well-known location
(e.g., "/images/.well-known/") would increase the risks of
colliding with a preexisting URI on a s
RFC 8615 (and RFC 5785 before it) says that .well-known should be at the
root of the URI local-part. Appendix A explains the rationale.
However, I'm seeing multi-tenancy in OpenID, with URI local-parts of the
form /${tenant}/.well-known/openid-configuration, which is not the
intended usage. /.we
