[GH-ISSUE #5408] [feature]: Show GraphQL response HTTP headers in the GraphQL tab #2076

New issue

Open

opened 2026-03-16 23:05:17 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 23:05:17 +03:00

Owner

Originally created by @marcelocastilho on GitHub (Sep 26, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5408

Is there an existing issue for this?

I have searched the existing issues

Summary

Problem When executing GraphQL requests in Hoppscotch, the UI does not display the HTTP response headers (e.g. cache-control, set-cookie, x-request-id, tracing headers, CORS-related headers). In the REST tab these metadata are visible and useful for debugging, but the GraphQL tab currently lacks this visibility.

Why this matters

Debugging: Helps diagnose caching (Cache-Control, ETag), CDN layers, auth/session issues (Set-Cookie), and rate limiting.
Observability: Trace propagation headers (traceparent, x-request-id) are essential in distributed systems.
Security review: Ability to inspect security-related headers (Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, etc.).
Consistency: REST and GraphQL tabs should offer a comparable inspection experience.
Requested behavior Add a Headers (or Response Headers) panel for GraphQL requests showing:

Full list of raw response headers (name → value).
Ability to copy one header or copy all.
(Optional) Quick filter/search.

Why should this be worked on?

Currently, when working with APIs in Hoppscotch, the REST tab displays all HTTP response headers, which helps with debugging, tracing, security, and understanding API behaviors. However, the GraphQL tab does not show these headers, making it harder for users to inspect caching, authentication, rate limiting, and tracing information for GraphQL responses. Adding this feature will make the experience more consistent, improve troubleshooting for developers, and allow better visibility into server-side metadata for GraphQL APIs. This is particularly important for teams doing API observability, debugging distributed systems, or working with proxies/CDNs, where response headers often contain critical information.

Originally created by @marcelocastilho on GitHub (Sep 26, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5408 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Problem When executing GraphQL requests in Hoppscotch, the UI does not display the HTTP response headers (e.g. cache-control, set-cookie, x-request-id, tracing headers, CORS-related headers). In the REST tab these metadata are visible and useful for debugging, but the GraphQL tab currently lacks this visibility. Why this matters Debugging: Helps diagnose caching (Cache-Control, ETag), CDN layers, auth/session issues (Set-Cookie), and rate limiting. Observability: Trace propagation headers (traceparent, x-request-id) are essential in distributed systems. Security review: Ability to inspect security-related headers (Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, etc.). Consistency: REST and GraphQL tabs should offer a comparable inspection experience. Requested behavior Add a Headers (or Response Headers) panel for GraphQL requests showing: Full list of raw response headers (name → value). Ability to copy one header or copy all. (Optional) Quick filter/search. ### Why should this be worked on? Currently, when working with APIs in Hoppscotch, the REST tab displays all HTTP response headers, which helps with debugging, tracing, security, and understanding API behaviors. However, the GraphQL tab does not show these headers, making it harder for users to inspect caching, authentication, rate limiting, and tracing information for GraphQL responses. Adding this feature will make the experience more consistent, improve troubleshooting for developers, and allow better visibility into server-side metadata for GraphQL APIs. This is particularly important for teams doing API observability, debugging distributed systems, or working with proxies/CDNs, where response headers often contain critical information.

kerem added the

feature

label

2026-03-16 23:05:17 +03:00

kerem commented

2026-03-16 23:05:28 +03:00

Author

Owner

@njfletcher215 commented on GitHub (Sep 26, 2025):

I am happy to work on this, please assign to me.

@njfletcher215 commented on GitHub (Sep 26, 2025): I am happy to work on this, please assign to me.

kerem commented

2026-03-16 23:05:33 +03:00

Author

Owner

@crunchydosa123 commented on GitHub (Sep 28, 2025):

Hey, is this being worked on? Would be happy to contribute here!

@crunchydosa123 commented on GitHub (Sep 28, 2025): Hey, is this being worked on? Would be happy to contribute here!

kerem commented

2026-03-16 23:05:38 +03:00

Author

Owner

@njfletcher215 commented on GitHub (Sep 29, 2025):

Go ahead.

@njfletcher215 commented on GitHub (Sep 29, 2025): Go ahead.

kerem commented

2026-03-16 23:05:43 +03:00

Author

Owner

@Sambhram1 commented on GitHub (Oct 4, 2025):