Skip to main content
The 2024 Developer Survey results are live! See the results
11 events
when toggle format what by license comment
Jul 6, 2022 at 15:04 comment added user1768761 I needed to append .then(r => r.json()) to the fetch call to see the response on the network tab.
Dec 5, 2019 at 19:21 comment added Michael I assume this won't work if developer tools weren't open when the request was made? I can see the URL as an error in the console (ERR_CONNECTION_TIMED_OUT) but when I try to open the link it sends a GET request, when the original was a POST. (As developer tools weren't open at the time, there is no Network entry)
Mar 6, 2019 at 1:22 history edited Michel CC BY-SA 4.0
Formatting
Mar 6, 2019 at 1:09 history edited Michel CC BY-SA 4.0
remove obsolete part
Jan 1, 2018 at 3:51 comment added Sameer Naik @madsobel late comment, but could not help. You can still execute curl from terminal as the request would have all the original cookies. It is same as replaying XHR from browser.
Oct 23, 2017 at 15:03 comment added CodeBrauer @afilina to even more automate this process you can add && open preview.html on macOS and the file opens directly after the request
Nov 17, 2015 at 22:05 comment added afilina Small trick: if you want to see cURL output in the browser, run it in the CLI like this curl ... > preview.html then open the file in the browser.
Mar 10, 2015 at 11:49 vote accept madsobel
Mar 2, 2015 at 2:04 history edited Michel CC BY-SA 3.0
Added info for Firefox
Feb 27, 2015 at 22:30 comment added madsobel This might actually be what I am looking for. I knew that I could copy the cURL call, but I could not run that from my terminal directly since I would get be authenticated. But with the terminal build in directly to Chorme, I'd assume that the call is made from "within" the browser. If so, then this should seal the deal.
Feb 27, 2015 at 22:21 history answered Michel CC BY-SA 3.0