Determine HTTP to HTTPS upgrade mechanism
Open
Nobody has claimed this yet.
doc: Protocol
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the discussion in issue #26, the linked TAG issue, the referenced RFC2817, and the 301 semantics discussion. Compare the HTTP-to-HTTPS upgrade mechanisms and document a decided mechanism and its RDF semantics for the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100