[GH-ISSUE #5276] [feature]: quickly view the complete request information #2019

Open
opened 2026-03-16 22:52:28 +03:00 by kerem · 4 comments
Owner

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?

  • I have searched the existing issues

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

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? - [x] I have searched the existing issues ### 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
Author
Owner

@Tathagata17 commented on GitHub (Sep 13, 2025):

Hi @faritor can you be more specific with any screenshot for the feature that you described.

<!-- gh-comment-id:3288028479 --> @Tathagata17 commented on GitHub (Sep 13, 2025): Hi @faritor can you be more specific with any screenshot for the feature that you described.
Author
Owner

@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

<!-- gh-comment-id:3657263671 --> @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
Author
Owner

@mmablom commented on GitHub (Dec 16, 2025):

In addition, here is a screenshot of the log in Postman:

Image

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.

<!-- gh-comment-id:3659886357 --> @mmablom commented on GitHub (Dec 16, 2025): In addition, here is a screenshot of the log in Postman: <img width="1914" height="301" alt="Image" src="https://github.com/user-attachments/assets/9d743142-38a9-41ad-a953-d93830e6a53a" /> 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.
Author
Owner

@mmgfrcs commented on GitHub (Dec 25, 2025):

Having #5582 will solve this

<!-- gh-comment-id:3691514350 --> @mmgfrcs commented on GitHub (Dec 25, 2025): Having #5582 will solve this
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#2019
No description provided.