New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix some 'nosniff' tests #27851
Fix some 'nosniff' tests #27851
Conversation
Heads up! This PR modifies the following files:
|
@bors-servo try=wpt |
Fix some 'nosniff' tests This PR implements some standard function to work with headers, hence it fixes some 'nosniff' test/ I create a PR as Draft because i have some questions: * i added the code info the `net` module instead of `script::dom::headers` to avoid some cyclic dependencies... but i'm not sure about this choice. Is there another potential location to put this code? * i used String object to match the spectification (it states to collect sequences of "code points", but some code use byte arrays. Should i change the code to work with bytes? --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [ ] These changes fix #___ (GitHub issue number if applicable) <!-- Either: --> - [x] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
☀️ Test successful - status-taskcluster |
☔ The latest upstream changes (presumably #27962) made this pull request unmergeable. Please resolve the merge conflicts. |
I rebased onto master. I think i'll needs these changes for future works. |
@bors-servo r+ |
📌 Commit 3b38240 has been approved by |
☀️ Test successful - status-taskcluster |
This PR implements some standard function to work with headers, hence it fixes some 'nosniff' test/
I create a PR as Draft because i have some questions:
net
module instead ofscript::dom::headers
to avoid some cyclic dependencies... but i'm not sure about this choice. Is there another potential location to put this code?./mach build -d
does not report any errors./mach test-tidy
does not report any errors