-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for URI Template #18
Comments
I plan to solve this problem when IETF proposes any new standards in extension to RFC 8484. At that time it will be clear how we can solve the problem. Prior to that, it is worth mentioning that we still need to maintain compatibility to Google DoH for the following reason:
Please discuss if anyone can come up with an idea to maintain compatibility and adapt URI Template. |
Has this changed in the last ~2 years? |
It seems that no DoH server really relies on the URI template feature, although it is specified in the RFC. I would rather leave current code as is. |
So this is still an issue, patches are welcome. But it currently bothers nobody even kept unfixed, and unfortunately my life is getting busy and can't afford allocating efforts to fix this issue. I prefer to keep it unfixed. |
IETF DoH requires a URI Template while configuring the client.
For example:
/query{?dns}
This implementation does not support URI Template yet, and still uses the obsolete
ct=
parameter to negotiate protocols. We need to eventually switch to URI Template in the future.But since it does not affect compatibility (either client or server side), and I do not have a clear understanding of it until the next extension of the protocol is published, I plan to leave this issue open and postpone this.
And as always, pull request is welcome.
The text was updated successfully, but these errors were encountered: