headers-assq vs headers-assq*
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 99
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
From RFC2616 Hypertext Transfer Protocol -- HTTP/1.1, section 4.2 (link):
Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.
It appears there is a headers-assq which is case-sensitive and a headers-assq* which is not case-sensitive.
Would it make sense to merge these two procedures into one that is strictly case-insensitive?
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the headers-assq and headers-assq* procedures in the web-server source, then read RFC2616 section 4.2 as referenced in the issue. Compare their case-sensitivity behavior and determine the compatibility implications of merging them; done means the API direction and resulting behavior are clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100