Closed
Bug 1810253
Opened 1 year ago
Closed 1 year ago
HTTP server doesn't support trailing slashes
Categories
(Remote Protocol :: CDP, defect, P5)
Tracking
(firefox111 fixed)
RESOLVED
FIXED
111 Branch
| Tracking | Status | |
|---|---|---|
| firefox111 | --- | fixed |
People
(Reporter: canadahonk, Assigned: canadahonk)
Details
Attachments
(1 file)
Steps to reproduce:
The CDP HTTP server listeners don't support trailing slashes, unlike Chromium which does, so could lead to potential problems due to the difference. Example: requesting /json/protocol/ (which is said in the CDP docs but trailing slash is probably a mistake).
Actual results:
Firefox gives 404 not found
Expected results:
It should treat /json/protocol/ like /json/protocol, etc.
|
Assignee | |
Comment 1•1 year ago
|
||
Added support for trailing slashes when using HTTP endpoints
(eg: /json/protocol/), previously they would return 404, not conforming
with CDP docs / expected result. Also added tests for such cases.
|
||
Updated•1 year ago
|
Assignee: nobody → oj
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
|
||
Updated•1 year ago
|
Severity: -- → S3
Priority: -- → P5
|
|
||
Updated•1 year ago
|
Attachment #9312338 -
Attachment description: Bug 1810253 - [cdp] Support trailing slashes for http endpoints → WIP: Bug 1810253 - [cdp] Support trailing slashes for http endpoints
|
|
||
Updated•1 year ago
|
Attachment #9312338 -
Attachment description: WIP: Bug 1810253 - [cdp] Support trailing slashes for http endpoints → Bug 1810253 - [cdp] Support trailing slashes for http endpoints
|
|
||
Updated•1 year ago
|
Attachment #9312338 -
Attachment description: Bug 1810253 - [cdp] Support trailing slashes for http endpoints → Bug 1810253 - [cdp] Support trailing slashes for supported JSONHandler endpoints
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0bdd0f580b6b [cdp] Support trailing slashes for supported JSONHandler endpoints r=webdriver-reviewers,whimboo
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•