quic: sendHeaders with non conforming path
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
While writing a webtransport test, I forgot on the client side a beginning '/' in the path, so something like ':path': 'testwtpath' . I do not think that this was reported back to js side on the server side. (it is detected in side nghttp3).
I wonder if this is a problem or if the behaviour is fine.
(I did not looked deeper into it, it was just by accident or stupidity).
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
Start at the QUIC sendHeaders entry point and reproduce the WebTransport case with a :path value missing its leading slash. Compare the behavior visible to JavaScript with the validation detected by nghttp3; done means the expected handling is established and covered by an appropriate regression test or clarified as valid behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100