Fine tune wording of the requirement for including Content-Type in the response
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the specification text containing the Content-Type requirement and the cited wording about responses to HEAD requests. Compare the terminology with the referenced RFC discussion, then update the requirement so its scope and HEAD-request applicability are explicit and technically consistent.
Written by the indexing model from the issue text.
Description
Extracting from: https://github.com/solid/specification/pull/561#discussion_r1305914478
In short, we want to make sure that the work makes it clear that it also applies when responding to HEAD requests.
@woutermont proposed
Server MUST generate a
Content-Typeheader field in a message that contains a representation, even if that representation only consists of representation metadata, as in aHEADrequest.
I think this is clear and concise. Maybe adjusting the last sentence to , as in a response to HEAD request
Since the wording in the spec includes nuances like
In a response to a HEAD request, the representation header fields describe the representation data that would have been enclosed in the content if the same request had been a GET
we should triple-check if we use all the terms strictly as intended by the RFC.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 110
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
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.
More from solid/specification
-
new-work-item
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#806 · 11 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#804 · 9 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
solid/specification#799 · 1 reaction ·
-
topic: resource access
Difficulty 5/5 Over a week Newbie friendliness 30/100
solid/specification#797 · 4 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/specification#788 · 4 comments · 1 reaction ·
All issues in solid/specification
Similar issues
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GDQuest/learn-gdscript#1395 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
HttpClient
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
symfony/symfony-docs#23092 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·