Closed
Bug 1903821
Opened 1 year ago
Closed 1 year ago
Using a redirect status code with network.provideResponse does not trigger a redirect
Categories
(Remote Protocol :: WebDriver BiDi, defect)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jdescottes, Unassigned)
References
Details
With the initial implementation of provideResponse for beforeRequestSent, some status codes do not behave as expected. For instance returning a 302 status code with a location header does not lead to a redirect.
This blocks the puppeteer test "request interception Request.respond should redirect" (both in requestinterception and requestinterception-experimental)
|
Reporter | |
Updated•1 year ago
|
Points: --- → 5
Priority: -- → P2
Whiteboard: [webdriver:m12]
|
|
Reporter | |
Comment 1•1 year ago
|
||
In the end the initial implementation for Bug 1853882 already supports this.
Status: NEW → RESOLVED
Points: 5 → ---
Closed: 1 year ago
Priority: P2 → --
Resolution: --- → INVALID
Whiteboard: [webdriver:m12]
You need to log in
before you can comment on or make changes to this bug.
Description
•