[GH-ISSUE #3584] Prettier for RAW responses #1231

Closed
opened 2026-03-16 19:25:42 +03:00 by kerem · 10 comments
Owner

Originally created by @spiderock98 on GitHub (Nov 22, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3584

Is there an existing issue for this?

  • I have searched the existing issues

Summary

When server response data is array of object . It cannot be format as JSON pretty version. I found in setting and docs but cannot find any config for this. Thank you for review

image

Why should this be worked on?

I think this is a basicly feature

Originally created by @spiderock98 on GitHub (Nov 22, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3584 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary When server response data is array of object . It cannot be format as JSON pretty version. I found in setting and docs but cannot find any config for this. Thank you for review ![image](https://github.com/hoppscotch/hoppscotch/assets/28623503/5d0527b8-d626-44a7-babb-4ce6e8f1cbc5) ### Why should this be worked on? I think this is a basicly feature
kerem 2026-03-16 19:25:42 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@liyasthomas commented on GitHub (Nov 22, 2023):

This might be because the response has an incorrect Content-Type header. Usually, JSON responses have a Content-Type: application/json which we check internally to prettify and format the response.

Can you confirm the response headers list has a proper Content-Type associated with JSON?

<!-- gh-comment-id:1823099259 --> @liyasthomas commented on GitHub (Nov 22, 2023): This might be because the response has an incorrect `Content-Type` header. Usually, JSON responses have a `Content-Type: application/json` which we check internally to prettify and format the response. Can you confirm the response headers list has a proper `Content-Type` associated with JSON?
Author
Owner

@spiderock98 commented on GitHub (Nov 22, 2023):

This might be because the response has an incorrect Content-Type header. Usually, JSON responses have a Content-Type: application/json which we check internally to prettify and format the response.

Can you confirm the response headers list has a proper Content-Type associated with JSON?

I have re-check and realize it just plain/text . I still hope there will parse json pretty despite of plain/text . because Postman and Insomnia still prettier plaintext data . btw Hoppscoth is super lightweight and fast ❤️

<!-- gh-comment-id:1823217322 --> @spiderock98 commented on GitHub (Nov 22, 2023): > This might be because the response has an incorrect `Content-Type` header. Usually, JSON responses have a `Content-Type: application/json` which we check internally to prettify and format the response. > > Can you confirm the response headers list has a proper `Content-Type` associated with JSON? I have re-check and realize it just plain/text . I still hope there will parse json pretty despite of plain/text . because Postman and Insomnia still prettier plaintext data . btw Hoppscoth is super lightweight and fast ❤️
Author
Owner

@marlonbasten commented on GitHub (Nov 22, 2023):

I will add something to that which may be a bit off-topic. This probably wouldn't have happened if you could set default headers at collection level. This is the main thing keeping me away from Hoppscotch. It's unusable if you have to define the Response type and API key for every single request. Imagine changing your api key on a collection with 300 requests.

<!-- gh-comment-id:1823608827 --> @marlonbasten commented on GitHub (Nov 22, 2023): I will add something to that which may be a bit off-topic. This probably wouldn't have happened if you could set default headers at collection level. This is the main thing keeping me away from Hoppscotch. It's unusable if you have to define the Response type and API key for every single request. Imagine changing your api key on a collection with 300 requests.
Author
Owner

@liyasthomas commented on GitHub (Nov 23, 2023):

Hi @marlonbasten, we’re working on collection level headers and authorization feature, expected to be released by December. Track its progress on #2259.

<!-- gh-comment-id:1823755401 --> @liyasthomas commented on GitHub (Nov 23, 2023): Hi @marlonbasten, we’re working on collection level headers and authorization feature, expected to be released by December. Track its progress on #2259.
Author
Owner

@spiderock98 commented on GitHub (Nov 23, 2023):

I will add something to that which may be a bit off-topic. This probably wouldn't have happened if you could set default headers at collection level. This is the main thing keeping me away from Hoppscotch. It's unusable if you have to define the Response type and API key for every single request. Imagine changing your api key on a collection with 300 requests.

I add middleware to modify response header and it all works fine now

<!-- gh-comment-id:1823761314 --> @spiderock98 commented on GitHub (Nov 23, 2023): > I will add something to that which may be a bit off-topic. This probably wouldn't have happened if you could set default headers at collection level. This is the main thing keeping me away from Hoppscotch. It's unusable if you have to define the Response type and API key for every single request. Imagine changing your api key on a collection with 300 requests. I add middleware to modify response header and it all works fine now
Author
Owner

@jackdewhurst commented on GitHub (Mar 19, 2024):

Is there any scope to add auto detect or an override feature to response formatting? Similarly to how Postman/Insomnia do it?

I don't want to have to add middleware in order to have my HTML responses formatted as JSON.

<!-- gh-comment-id:2006907699 --> @jackdewhurst commented on GitHub (Mar 19, 2024): Is there any scope to add auto detect or an override feature to response formatting? Similarly to how Postman/Insomnia do it? I don't want to have to add middleware in order to have my HTML responses formatted as JSON.
Author
Owner

@koldle commented on GitHub (Jun 7, 2024):

Hi @liyasthomas, I believe this issue has not been resolved. Setting request headers at the collection level does not solve the problem of response body formatting for non-JSON response headers. Could you please reopen this issue?

<!-- gh-comment-id:2153721148 --> @koldle commented on GitHub (Jun 7, 2024): Hi @liyasthomas, I believe this issue has not been resolved. Setting request headers at the collection level does not solve the problem of response body formatting for non-JSON response headers. Could you please reopen this issue?
Author
Owner

@lukepighetti commented on GitHub (Jun 20, 2024):

a lot of json endpoints return the wrong content type, we should still try to format them, imo

<!-- gh-comment-id:2181205026 --> @lukepighetti commented on GitHub (Jun 20, 2024): a lot of json endpoints return the wrong content type, we should still try to format them, imo
Author
Owner

@linto11 commented on GitHub (Dec 31, 2024):

do we have a fix for this?

<!-- gh-comment-id:2566173147 --> @linto11 commented on GitHub (Dec 31, 2024): do we have a fix for this?
Author
Owner

@Phaired commented on GitHub (May 7, 2025):

Is there still no workaround or fix? This is very annoying for a poorly designed API.

<!-- gh-comment-id:2857700082 --> @Phaired commented on GitHub (May 7, 2025): Is there still no workaround or fix? This is very annoying for a poorly designed API.
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#1231
No description provided.