starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #4617] [bug]: Why would header If-None-Match be included into repetitive GET requests? #1713

New issue

Closed

opened 2026-03-16 21:30:17 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 21:30:17 +03:00

Owner

Originally created by @abatishchev on GitHub (Dec 14, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4617

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I make repetitive GET requests to a web service I don't control (Azure Resource Manager, ARM) and do it quickly enough, Hoppscotch includes header If-None-Match which causes a failure.

Hoppscotch is a RESTful API testing tool, so I'd expect it not to include additional headers until instructed. I searched for settings to disable the behavior, but I couldn't find any.

Steps to reproduce

See above

Environment

Production

Version

Self-hosted, v2024.11.0

Originally created by @abatishchev on GitHub (Dec 14, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4617 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I make repetitive GET requests to a web service I don't control (Azure Resource Manager, ARM) and do it quickly enough, Hoppscotch includes header `If-None-Match` which causes a failure. Hoppscotch is a RESTful API testing tool, so I'd expect it not to include additional headers until instructed. I searched for settings to disable the behavior, but I couldn't find any. ### Steps to reproduce See above ### Environment Production ### Version Self-hosted, v2024.11.0

kerem

2026-03-16 21:30:17 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 21:30:33 +03:00

Author

Owner

@abatishchev commented on GitHub (Feb 9, 2025):

Bump

@abatishchev commented on GitHub (Feb 9, 2025): Bump

kerem commented

2026-03-16 21:30:38 +03:00

Author

Owner

@abatishchev commented on GitHub (Feb 5, 2026):

Bump

@abatishchev commented on GitHub (Feb 5, 2026): Bump

kerem commented

2026-03-16 21:30:44 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 5, 2026):

Hi @abatishchev, Hoppscotch itself doesn’t inject the If-None-Match header.

The If-None-Match header is sent by browsers automatically when requesting a resource they have already cached, containing the ETag of that cached resource. This allows the browser to ask the server if the resource has changed, and if not, the server responds with a 304 Not Modified status, instructing the browser to use its cached version, which saves bandwidth and provides a faster user experience.

If you’re using Hoppscotch client from a web browser, I recommend enabling the Agent mode or Proxy mode from Settings > Interceptor. Alternatively, you can download the desktop app and use Native interceptor mode.

Since the Hoppscotch client doesn’t inject the If-None-Match header automatically, and it’s a native browser API response, I’m afraid we don’t have control over how the browser intercepts the request, except for the alternatives mentioned above.

@liyasthomas commented on GitHub (Feb 5, 2026): Hi @abatishchev, Hoppscotch itself doesn’t inject the `If-None-Match` header. > The `If-None-Match` header is sent by browsers automatically when requesting a resource they have already cached, containing the ETag of that cached resource. This allows the browser to ask the server if the resource has changed, and if not, the server responds with a 304 Not Modified status, instructing the browser to use its cached version, which saves bandwidth and provides a faster user experience. If you’re using Hoppscotch client from a web browser, I recommend enabling the Agent mode or Proxy mode from Settings > Interceptor. Alternatively, you can [download the desktop app](https://hoppscotch.com/download) and use Native interceptor mode. Since the Hoppscotch client doesn’t inject the `If-None-Match` header automatically, and it’s a native browser API response, I’m afraid we don’t have control over how the browser intercepts the request, except for the alternatives mentioned above.

kerem commented

2026-03-16 21:30:49 +03:00

Author

Owner

@abatishchev commented on GitHub (Feb 5, 2026):

@liyasthomas fair enough, thanks for the explanation!

@abatishchev commented on GitHub (Feb 5, 2026): @liyasthomas fair enough, thanks for the explanation!