[GH-ISSUE #5627] [feature]: Add request body tab #2177

Open
opened 2026-03-16 23:29:15 +03:00 by kerem · 1 comment
Owner

Originally created by @JohannesBe on GitHub (Nov 28, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5627

Is there an existing issue for this?

  • I have searched the existing issues

Summary

It is not always clear exactly what was sent over the wire (RAW).

  1. when you commented out lines
  2. When you use variables in hoppscotch request bodies (especially with randomly generated ones)
  3. Other postprocessing done by hoppscotch (?)

This makes it really hard to debug requests that were sent over the wire in some cases.

Proposal: in the respons body pane, also add a Request tab that shows the exact, unaltered body that was sent over the wire.

Why should this be worked on?

Right now it is hard to debug when requests fail.

Originally created by @JohannesBe on GitHub (Nov 28, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5627 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary It is not always clear exactly _what_ was sent over the wire (RAW). 1) when you commented out lines 2) When you use variables in hoppscotch request bodies (especially with randomly generated ones) 3) Other postprocessing done by hoppscotch (?) This makes it really hard to debug requests that were sent over the wire in some cases. Proposal: in the respons body pane, also add a `Request` tab that shows the _exact_, unaltered body that was sent over the wire. ### Why should this be worked on? Right now it is hard to debug when requests fail.
Author
Owner

@JohannesBe commented on GitHub (Nov 28, 2025):

FYI: #3904 could also reduce the gravity of this problem (i.e. then you could do a console.log(pw.request)

<!-- gh-comment-id:3588684970 --> @JohannesBe commented on GitHub (Nov 28, 2025): FYI: #3904 could also reduce the gravity of this problem (i.e. then you could do a `console.log(pw.request)`
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#2177
No description provided.