Copy as cURL (POSIX) adds ^ in front of query params separator (^&)
Categories
(DevTools :: Netmonitor, defect, P2)
Tracking
(firefox-esr115 wontfix, firefox-esr128 wontfix, firefox-esr140 wontfix, firefox139 wontfix, firefox140 wontfix, firefox141 wontfix, firefox142 fixed)
People
(Reporter: gregoire.piat, Assigned: bomsy)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0
Steps to reproduce:
Version: 140.0b4 on Windows
I went to a website using REST APIs with query params.
I opened the dev tools and went to the Network tab.
I selected a network call with an URL containing query params separated by & character.
I did a right click -> Copy as cURL (POSIX)
Can be reproduced on https://datausa.io/api/data?drilldowns=Nation&measures=Population
Actual results:
On my clipboard, I had the following value
curl 'https://datausa.io/api/data?drilldowns=Nation^&measures=Population'
--compressed
-H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0'
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8'
-H 'Accept-Language: en-US,en;q=0.8,fr;q=0.5,fr-FR;q=0.3'
-H 'Accept-Encoding: gzip, deflate, br, zstd'
-H 'DNT: 1'
-H 'Connection: keep-alive'
-H 'Upgrade-Insecure-Requests: 1'
-H 'Sec-Fetch-Dest: document'
-H 'Sec-Fetch-Mode: navigate'
-H 'Sec-Fetch-Site: cross-site'
-H 'Sec-GPC: 1'
-H 'Priority: u=0, i'
-H 'Pragma: no-cache'
-H 'Cache-Control: no-cache'
-H 'TE: trailers'
You can notice that the URL contains a ^&
Expected results:
I should not have a ^ in front of the & query param separator.
I should have following value in my clipboard:
curl 'https://datausa.io/api/data?drilldowns=Nation&measures=Population'
--compressed
-H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0'
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8'
-H 'Accept-Language: en-US,en;q=0.8,fr;q=0.5,fr-FR;q=0.3'
-H 'Accept-Encoding: gzip, deflate, br, zstd'
-H 'DNT: 1'
-H 'Connection: keep-alive'
-H 'Upgrade-Insecure-Requests: 1'
-H 'Sec-Fetch-Dest: document'
-H 'Sec-Fetch-Mode: navigate'
-H 'Sec-Fetch-Site: cross-site'
-H 'Sec-GPC: 1'
-H 'Priority: u=0, i'
-H 'Pragma: no-cache'
-H 'Cache-Control: no-cache'
-H 'TE: trailers'
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1950001
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
This will not make beta for Fx140, but we could take it as a ride-along later (RC/dot release)
Please add a release uplift request when this is ready.
It looks like it's needed on ESR also, so it will need uplift requests there too.
Comment 6•1 year ago
|
||
The bug is marked as tracked for firefox140 (beta). However, the bug still has low severity.
:Honza, could you please increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 7•1 year ago
|
||
This is tracked for release as requested last week.
Fx141 goes to beta on Monday. This will also need an beta uplift if it doesn't land before Merge Day.
Updated•1 year ago
|
Comment 8•1 year ago
|
||
Set release status flags based on info from the regressing bug 1950001
Comment 9•1 year ago
|
||
:bomsy, this is tracked for release as requested.
Fx140 is now live, but there is a planned dot release in a couple of weeks.
We can include this if it's safe to include as a ride along? Release uplift request needed by eod on 2026-06-04
Updated•1 year ago
|
| Assignee | ||
Comment 10•1 year ago
|
||
(In reply to Donal Meehan [:dmeehan] from comment #9)
:bomsy, this is tracked for release as requested.
Fx140 is now live, but there is a planned dot release in a couple of weeks.
We can include this if it's safe to include as a ride along? Release uplift request needed by eod on 2026-06-04
Sure, that sounds fine. Once reviewed. thanks Donal.
Comment 11•1 year ago
|
||
Let's review the current patch and land this + uplift to beta potentially. Then file a followup to remove the cross platform escaping and clarify the situation with security team.
Updated•1 year ago
|
Comment 12•1 year ago
|
||
(In reply to Hubert Boma Manilla (:bomsy) from comment #10)
(In reply to Donal Meehan [:dmeehan] from comment #9)
:bomsy, this is tracked for release as requested.
Fx140 is now live, but there is a planned dot release in a couple of weeks.
We can include this if it's safe to include as a ride along? Release uplift request needed by eod on 2026-06-04Sure, that sounds fine. Once reviewed. thanks Donal.
This is not on track to make the Fx140 planned dot release.
It would need to land in central, beta and get a release request uplift by EOD Friday 2025-07-04.
Comment 13•1 year ago
|
||
It's too late for Fx140
:bomesy, next week is the final week of beta for Fx141, so there is little time to land and uplift
Updated•1 year ago
|
| Assignee | ||
Comment 14•1 year ago
|
||
(In reply to Donal Meehan [:dmeehan] from comment #13)
It's too late for Fx140
:bomesy, next week is the final week of beta for Fx141, so there is little time to land and uplift
Hi Donal,
Thanks for the reminder. We decided to undo the work in bug 1950001 which led to this issue. The revert is being done in Bug 1974973.
We should be able to close this once that lands. Thanks
| Assignee | ||
Comment 15•1 year ago
|
||
Closing this as Bug 1974973 has landed
Updated•1 year ago
|
Description
•