network.continueRequest does not support multiple values for the same header name
Categories
(Remote Protocol :: WebDriver BiDi, defect, P2)
Tracking
(firefox129 fixed)
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m11][wptsync upstream][webdriver:relnote])
Attachments
(2 files)
The BiDi spec for continueRequest does not restrict headers to a single value per name.
It should be possible to set multiple values for a single header name.
Technically setting nameA:value1
+ nameA:value2
is equivalent to nameA:value1, value2
, so we should support that.
At the moment Firefox will only set nameA:value2
Assignee | ||
Comment 1•8 months ago
|
||
Updated•8 months ago
|
Assignee | ||
Comment 2•8 months ago
|
||
I spotted this issue while looking at puppeteer tests for provideResponse. I used merge=false when calling the APIs to setRequestHeaders for network.continueRequest, but in theory we should support multiple header values.
Assignee | ||
Comment 3•8 months ago
|
||
Depends on D214730
Assignee | ||
Updated•8 months ago
|
Comment 5•8 months ago
|
||
Backed out for causing failures in cookies.py
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | /webdriver/tests/bidi/network/continue_request/cookies.py | test_override_modified_header_cookies - AssertionError
Assignee | ||
Comment 6•8 months ago
|
||
For scenarios where we have both a cookie header and cookies parameters we actually should NOT merge.
Comment 9•8 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a7726ece8e7f
https://hg.mozilla.org/mozilla-central/rev/d08a4c993db0
Updated•7 months ago
|
Description
•