-
Notifications
You must be signed in to change notification settings - Fork 87
HTTPS #6
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
Comments
Sorry, just saw the reference in section 5.4. Again, though a best practice statement at minimum might be warranted. |
What kind of best practice statement do you have in mind? Could you make a proposal that we can discuss? |
@cportele Was thinking of something along the lines of https://https.cio.gov/ |
Discussed during the meeting on 2017-11-28: The current text seems sufficient for now. If we identify in the period where we will work on implementations of the specification that more guidance is needed (e.g., on redirects from http to https), we will add it. |
Does there need to be any discussion around secure channel (e.g. HTTPS) vs HTTP? How about protocol-relative URI's? I understand that it's an anti-pattern. A best practice might be warranted.
The text was updated successfully, but these errors were encountered: