mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5276] [feature]: quickly view the complete request information #2019
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2019
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @faritor on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5276
Is there an existing issue for this?
Summary
thank you to the developer team for providing such an excellent product
when I use the Pre-request script, where should I be able to see the final complete url address of the request I initiated, the information such as header, body, and query, as well as the header and body in the response In Postman, you can easily view this information in the console
when will the collection-level pre-request plan be supported? I saw an issue from a long time ago, but there was no response
Why should this be worked on?
I hope this issue can be optimized
@Tathagata17 commented on GitHub (Sep 13, 2025):
Hi @faritor can you be more specific with any screenshot for the feature that you described.
@21307369 commented on GitHub (Dec 15, 2025):
After a request made with a Pre-request script, the full request URL address cannot be copied, making repeated requests in the browser.
After using the order number, timestamp, and encryption-related algorithms in the script, you need to use the actual requested url to request again. The common practice is to copy it to the browser and request again to reproduce the bug.
And request time, response time
@mmablom commented on GitHub (Dec 16, 2025):
In addition, here is a screenshot of the log in Postman:
As others have mentioned it's sometimes very useful to be able to see the full, raw, actual request that was sent from Hoppscotch. For instance when using variables, URL encoding and/or pre-request scripts. Seeing the actual request makes it easier to spot where a mistake was made.
In addition, this would also be useful for when an OAuth request fails in the collection authorization tab. Currently it requires sifting through the request in the network log to see what the actual error was from the API and presenting all request through a console/log would allow for easier debugging in such cases.
@mmgfrcs commented on GitHub (Dec 25, 2025):
Having #5582 will solve this