Closed Bug 1448210 Opened 6 years ago Closed 6 years ago

FIrefox 59.0.1 (64-bit) on mac "copy as curl" not working correctly.

Categories

(DevTools :: General, defect, P1)

59 Branch
x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1269468

People

(Reporter: ripley.net, Unassigned)

Details

(Whiteboard: [specification][type:bug])

What did you do?
================
1. Open Firefox 59.0.1 (64-bit) on Mac Pro.
2. Open developer tool (Cmd+Shift+i)
3. Open a website under test
4. Click a link which send a post request with JSON body
5. In developer tool right click on the request and click "Copy as curl"

What happened?
==============
The request is copied but the data part is missing.
It's copied as ...
curl 'https://1.2.3.4/rest-api/v100/session/manager/session/active' -H 'Accept: application/json' --compressed -H 'Accept-Language: en-US,en;q=0.5' -H 'Authorization: Basic 32cdd809-ed54-4c5f-96a5-54ae3ae7874e' -H 'BasicBypassBrowserHandling: true' -H 'Cache-Control: no-cache' -H 'Connection: keep-alive' -H 'Content-Type: application/json' -H 'Cookie: _pk_id.1.f52c=9c5405c51ea8371a.1521008814.10.1521773066.1521773055..; CID=BgAAAAOzvzGhKcauuDUB4Zc89RE=; session_token=xxxyyyzzz; _pk_ses.1.f52c=0' -H 'Host: 3.4.5.6' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:59.0) Gecko/20100101 Firefox/59.0' --data ''

Notice the value arg --data is empty.

What should have happened?
==========================
Parameters of the request in web should be copied to curl request.

Is there anything else we should know?
======================================
Tried to do same thing in Chrome, and it's working.
Severity: normal → major
Component: General → Developer Tools
OS: Other → Mac OS X
Priority: -- → P1
Product: developer.mozilla.org → Firefox
Hardware: All → x86_64
Version: unspecified → 59 Branch
I believe this is a dupe of bug 1269468. Luckily it just got fixed yesterday :-)
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.