mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3538] [feature]: Content decoding HTTP Responses #1208
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#1208
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 @drewthor on GitHub (Nov 10, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3538
Is there an existing issue for this?
Summary
Compressed HTTP response bodies show up as binary bytes in the HTTP response. It would be incredibly helpful if Hoppscotch supported some of the most common
Content-EncodingResponse Header values and allowed the user to have the desktop app to decode the response to be able to see responses in human readable form.Why should this be worked on?
Not supporting decompression/decoding of compressed HTTP responses forces the user out of the Hoppscotch app when trying to test API responses and test their APIs. Having this functionality in Hoppscotch allows for the user to use the app as a one-stop-shop for all of their needs.
@adrianritchie commented on GitHub (Sep 9, 2024):
I have the same problem with Hoppscotch desktop v2024.8.1 on Windows 11.
However, cloning the repo at version tag and running Hoppscotch web in Chrome and Edge it works fine.
@liyasthomas commented on GitHub (Mar 4, 2025):
Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release.
Download the latest builds and provide your valuable feedback.
Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.