You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussed briefly in #26 , there are several upgrade mechanisms from HTTP to HTTPS. We currently suggest 301 but it doesn't seem very settled what the semantics of 301 in relation to RDF, even though it has been discussed for a long time. It was raised in the TAG but doesn't seem to have a conclusion.
There's also RFC2817.
The text was updated successfully, but these errors were encountered:
Somewhat orthogonal to the 3xx response code discussion, but perhaps we should also recommend the use of the Strict-Transport-Security header, defined in RFC 6797.
It's a SHOULD. (There are cases, such as testing and behind a reverse proxy, where you want the pod itself to run over HTTP.)
But even when HTTPS is required/used, we still need to be able to react to regular HTTP requests, namely by switching them to HTTPS. This issue specifies how.
Discussed briefly in #26 , there are several upgrade mechanisms from HTTP to HTTPS. We currently suggest
301
but it doesn't seem very settled what the semantics of301
in relation to RDF, even though it has been discussed for a long time. It was raised in the TAG but doesn't seem to have a conclusion.There's also RFC2817.
The text was updated successfully, but these errors were encountered: