starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #763] Request : Copy response headers #269

New issue

Closed

opened 2026-03-16 14:18:13 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 14:18:13 +03:00

Owner

Originally created by @rdhar on GitHub (Apr 12, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/763

Is your feature request related to a problem? Please describe.
Honestly, not really a problem as much as an improvement suggestion. Love this project and the ease-of-use brought about by it!

Describe the solution you'd like
Often, I compare response headers of different requests. Despite the clear display of headers information, there's no way to select all of the data together, let alone copy it to clipboard to paste and compare elsewhere. A button like "Copy response" for response headers would be ideal.

Describe alternatives you've considered
None that I'm currently aware of, beyond constantly switching between windows and copying one field at a time.

Additional context
Hopefully, I'm not the only who cares about copy-pasting headers. Please feel free to let me know if you'd like any more information I can help provide. Thanks for your time!

I'm using Chrome v81 on Windows 10 v1903.

Originally created by @rdhar on GitHub (Apr 12, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/763 **Is your feature request related to a problem? Please describe.** Honestly, not really a problem as much as an improvement suggestion. Love this project and the ease-of-use brought about by it! **Describe the solution you'd like** Often, I compare response headers of different requests. Despite the clear display of headers information, there's no way to select all of the data together, let alone copy it to clipboard to paste and compare elsewhere. A button like "Copy response" for response headers would be ideal. **Describe alternatives you've considered** None that I'm currently aware of, beyond constantly switching between windows and copying one field at a time. **Additional context** Hopefully, I'm not the only who cares about copy-pasting headers. Please feel free to let me know if you'd like any more information I can help provide. Thanks for your time! I'm using Chrome v81 on Windows 10 v1903.

kerem

2026-03-16 14:18:13 +03:00

closed this issue
added the
need information
label

kerem commented

2026-03-16 14:18:29 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 12, 2020):

There's already a "copy response" button that lets you to copy the entire response to clipboard, alog with download as JSON. If you insist, we can add a seperate copy button for headers even though it doesn't seems like an enhancement.

@liyasthomas commented on GitHub (Apr 12, 2020): There's already a "copy response" button that lets you to copy the entire response to clipboard, alog with download as `JSON`. If you insist, we can add a seperate _copy button for headers_ even though it doesn't seems like an enhancement. ![Screenshot_20200412-230709](https://user-images.githubusercontent.com/10395817/79075851-e8fd0200-7d12-11ea-9096-0ac540649abd.png)

kerem commented

2026-03-16 14:18:34 +03:00

Author

Owner

@rdhar commented on GitHub (Apr 12, 2020):

Thanks so much for your prompt response, @liyasthomas, I really appreciate it!

That's pretty curious because I don't seem have any of the headers available within the response panel, otherwise this would be complete non-issue. Could this be an API specific thing? For reference, I'm using PagerDuty API and this is what I see:

Only things of note is parameter PagerDuty's Accept: application/vnd.pagerduty+json;version=2. Might that be messing with the parsing?

@rdhar commented on GitHub (Apr 12, 2020): Thanks so much for your prompt response, @liyasthomas, I really appreciate it! That's pretty curious because I don't seem have any of the headers available within the response panel, otherwise this would be complete non-issue. Could this be an API specific thing? For reference, I'm using [PagerDuty API](https://developer.pagerduty.com/api-reference/) and this is what I see: ![image](https://user-images.githubusercontent.com/19497993/79076083-2ea7d380-7cef-11ea-86b6-c0121516b032.png) Only things of note is parameter PagerDuty's `Accept: application/vnd.pagerduty+json;version=2`. Might that be messing with the parsing?

kerem commented

2026-03-16 14:18:39 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 12, 2020):

can you share the endpoint without creds/token so that I could reproduce the issue at my end?

@liyasthomas commented on GitHub (Apr 12, 2020): can you share the endpoint without creds/token so that I could reproduce the issue at my end?

kerem commented

2026-03-16 14:18:44 +03:00

Author

Owner

@rdhar commented on GitHub (Apr 12, 2020):

Certainly, I should've shared it earlier: here's ONE from one endpoint and here's ANOTHER from a different endpoint altogether.

The accompanying cURL looks like:

curl -X GET 
  'https://api.pagerduty.com/incidents' 
  -H 'Accept: application/vnd.pagerduty+json;version=2' 
  -H 'Authorization: Token token=obfuscated' 

curl -X GET 
  'https://api.newrelic.com/v2/alerts_events.json' 
  -H 'Accept: application/json' 
  -H 'X-Api-Key: obfuscated'

Thanks once again for looking into this on my behalf, really grateful for your time (and patience!)

@rdhar commented on GitHub (Apr 12, 2020): Certainly, I should've shared it earlier: here's [ONE](https://postwoman.io/?method=GET&url=https://api.pagerduty.com&path=/incidents&headers=%5B%7B%22key%22:%22Accept%22,%22value%22:%22application/vnd.pagerduty+json;version=2%22%7D,%7B%22key%22:%22Authorization%22,%22value%22:%22Token%20token=obfuscated%22%7D,%7B%22key%22:%22%22,%22value%22:%22%22%7D%5D) from one endpoint and here's [ANOTHER](https://postwoman.io/?method=GET&url=https://api.newrelic.com&path=/v2/alerts_events.json&headers=%5B%7B%22key%22:%22Accept%22,%22value%22:%22application/json%22%7D,%7B%22key%22:%22X-Api-Key%22,%22value%22:%22%22%7D%5D&params=%5B%7B%22key%22:%22%22,%22value%22:%22%22%7D%5D) from a different endpoint altogether. The accompanying cURL looks like: ``` curl -X GET 'https://api.pagerduty.com/incidents' -H 'Accept: application/vnd.pagerduty+json;version=2' -H 'Authorization: Token token=obfuscated' curl -X GET 'https://api.newrelic.com/v2/alerts_events.json' -H 'Accept: application/json' -H 'X-Api-Key: obfuscated' ``` Thanks once again for looking into this on my behalf, really grateful for your time (and patience!)

kerem commented

2026-03-16 14:18:49 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 12, 2020):

Let me look into it. The response data surely plays an important role on how headers and other response fields are displayed. I'll update once I figure out a way to tackle this issue.

@liyasthomas commented on GitHub (Apr 12, 2020): Let me look into it. The response data surely plays an important role on how headers and other response fields are displayed. I'll update once I figure out a way to tackle this issue.

kerem commented

2026-03-16 14:18:54 +03:00

Author

Owner

@rdhar commented on GitHub (Apr 12, 2020):

Sounds good, just glad I hadn't overlooked a button that does this already!

It is kinda curious that the response headers are clearly found and parsed by Postwoman (screenshot attached below), even when they're not shown as part of the response body itself.

Hence, I do wonder if a separate Copy headers button might add some value to extract the relevant dataset regardless of response body format from various endpoints "standards".

@rdhar commented on GitHub (Apr 12, 2020): Sounds good, just glad I hadn't overlooked a button that does this already! It is kinda curious that the response headers are [clearly found and parsed by Postwoman](https://postwoman.io/?method=GET&url=https%3A%2F%2Fapi.newrelic.com&path=%2Fv2%2Falerts_events.json&headers=%5B%7B%22key%22%3A%22Accept%22,%22value%22%3A%22application%2Fjson%22%7D,%7B%22key%22%3A%22X-Api-Key%22,%22value%22%3A%22obfuscated%22%7D%5D&params=%5B%7B%22key%22%3A%22%22,%22value%22%3A%22%22%7D%5D) (screenshot attached below), even when they're not shown as part of the response body itself. Hence, I do wonder if a separate _Copy headers_ button might add some value to extract the relevant dataset regardless of response body format from various endpoints "standards". ![image](https://user-images.githubusercontent.com/19497993/79077195-8a765a80-7cf7-11ea-9afd-7bbb322b38d2.png)

kerem commented

2026-03-16 14:19:00 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 19, 2020):

seperate copy button for headers are not required.

@liyasthomas commented on GitHub (Apr 19, 2020): seperate copy button for headers are not required.

kerem referenced this issue

2026-03-17 00:13:29 +03:00

[PR #270] [MERGED] Fix #269 Incorrect code generation #2530