[GH-ISSUE #2095] [feature]: Disable redirects

kerem commented

2026-03-16 16:44:52 +03:00

Owner

Originally created by @KaKi87 on GitHub (Jan 28, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2095

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Summary

Disable redirects

Why should this be worked on?

Disable redirects

Originally created by @KaKi87 on GitHub (Jan 28, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2095 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Disable redirects ### Why should this be worked on? Disable redirects

kerem

2026-03-16 16:44:52 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 16:45:08 +03:00

Author

Owner

@iamajar commented on GitHub (Jun 28, 2022):

I need the feature too.
Just like the setting of Postman - "Automatically follow redirects : off".

@iamajar commented on GitHub (Jun 28, 2022): I need the feature too. Just like the setting of Postman - "Automatically follow redirects : off".

kerem commented

2026-03-16 16:45:13 +03:00

Author

Owner

@ghost commented on GitHub (Jul 10, 2022):

I need the feature too.
Sometimes we just need to see 302 Found

@ghost commented on GitHub (Jul 10, 2022): I need the feature too. Sometimes we just need to see `302 Found`

kerem commented

2026-03-16 16:45:18 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jul 13, 2022):

Sometimes we just need to see 302 Found

That is exactly the problem, since we are backed by the browser APIs at the end of the day, due to the Atomic HTTP Redirect Handling policy in the fetch implementation, we will not be able to get access to the redirect information. If we ask the browser to disable redirect, it will just send us out a generic network error where we can't guarantee whether it was a connectivity issue, invalid content or even a redirect.

See spec: https://fetch.spec.whatwg.org/#atomic-http-redirect-handling

This may be possible to be implemented in Proxyscotch tho.

I am keeping this issue open so we can eventually implement it when we are building the native app.

@AndrewBastin commented on GitHub (Jul 13, 2022): > Sometimes we just need to see 302 Found That is exactly the problem, since we are backed by the browser APIs at the end of the day, due to the Atomic HTTP Redirect Handling policy in the `fetch` implementation, we will not be able to get access to the redirect information. If we ask the browser to disable redirect, it will just send us out a generic network error where we can't guarantee whether it was a connectivity issue, invalid content or even a redirect. See spec: https://fetch.spec.whatwg.org/#atomic-http-redirect-handling This may be possible to be implemented in Proxyscotch tho. I am keeping this issue open so we can eventually implement it when we are building the native app.

kerem commented

2026-03-16 16:45:23 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jul 13, 2022):

This may be possible to be implemented in Proxyscotch tho.

Exactly, please.

we are building the native app

By native, do you mean non-Electron ?

@KaKi87 commented on GitHub (Jul 13, 2022): > This may be possible to be implemented in Proxyscotch tho. Exactly, please. > we are building the native app By native, do you mean non-Electron ?

kerem commented

2026-03-16 16:45:28 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jul 13, 2022):

Exactly, please.

Please create an issue in github.com/hoppscotch/proxyscotch so that can be tracked.

By native, do you mean non-Electron ?

Absolutely not, we are planning to go with Tauri, but this is still long ways off, I don't expect it to even be in an Alpha stage till 2023.

@AndrewBastin commented on GitHub (Jul 13, 2022): > Exactly, please. Please create an issue in github.com/hoppscotch/proxyscotch so that can be tracked. > By native, do you mean non-Electron ? Absolutely not, we are planning to go with Tauri, but this is still long ways off, I don't expect it to even be in an Alpha stage till 2023.

kerem commented

2026-03-16 16:45:33 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jul 14, 2022):

Please create an issue in github.com/hoppscotch/proxyscotch so that can be tracked.

Oh I'm sorry, I thought that was the extension.

Could the extension handle this ?

we are planning to go with Tauri

Nice !

this is still long ways off, I don't expect it to even be in an Alpha stage till 2023

What would take that long ?
Tauri's HTTP methods are easy enough to use so that I made an axios adapter for it.
Would you like a fetch adapter ?

@KaKi87 commented on GitHub (Jul 14, 2022): > Please create an issue in github.com/hoppscotch/proxyscotch so that can be tracked. Oh I'm sorry, I thought that was the extension. Could the extension handle this ? > we are planning to go with Tauri Nice ! > this is still long ways off, I don't expect it to even be in an Alpha stage till 2023 What would take that long ? Tauri's HTTP methods are easy enough to use so that I made an [`axios` adapter](https://git.kaki87.net/KaKi87/axios-tauri-adapter) for it. Would you like a `fetch` adapter ?

kerem commented

2026-03-16 16:45:38 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jul 14, 2022):

Could the extension handle this ?

AFAIK, I don't think so. Extension still uses the browser APIs for the most part.

What would take that long ?
Tauri's HTTP methods are easy enough to use so that I made an axios adapter for it.
Would you like a fetch adapter ?

Thank you for your suggestion (your code looks awesome! ❤️).

We are still a small team and we want to keep the web app as the main priority still. We believe the web app is the future for the most part and native is just a way to keep the app not limited due to browser issues meanwhile. We want to spend a lot of time, just figuring out how to make the development part really easy in a way that we can just build the web app and the native app together at the same time in a way that it is really clean because we think it is a worthwhile investment. So, I am working towards that for now.

You can DM me if you are interested in continuing the conversation as it is getting a bit off-topic. You can find me on the Hoppscotch Discord/Telegram (link in README).

@AndrewBastin commented on GitHub (Jul 14, 2022): > Could the extension handle this ? AFAIK, I don't think so. Extension still uses the browser APIs for the most part. > What would take that long ? Tauri's HTTP methods are easy enough to use so that I made an [axios adapter](https://git.kaki87.net/KaKi87/axios-tauri-adapter) for it. Would you like a fetch adapter ? Thank you for your suggestion (your code looks awesome! :heart:). We are still a small team and we want to keep the web app as the main priority still. We believe the web app is the future for the most part and native is just a way to keep the app not limited due to browser issues meanwhile. We want to spend a lot of time, just figuring out how to make the development part really easy in a way that we can just build the web app and the native app together at the same time in a way that it is really clean because we think it is a worthwhile investment. So, I am working towards that for now. You can DM me if you are interested in continuing the conversation as it is getting a bit off-topic. You can find me on the Hoppscotch Discord/Telegram (link in README).

kerem commented

2026-03-16 16:45:43 +03:00

Author

Owner

@drilus commented on GitHub (Oct 6, 2023):

I need this feature as well.

@drilus commented on GitHub (Oct 6, 2023): I need this feature as well.

kerem commented

2026-03-16 16:45:49 +03:00

Author

Owner

@Daanoz commented on GitHub (Nov 10, 2023):

As an alternative, would it be possible to expose the url where the request redirected to, in the pw.response object so it could be used in the scripts? https://docs.hoppscotch.io/documentation/features/scripts#pwresponse

@Daanoz commented on GitHub (Nov 10, 2023): As an alternative, would it be possible to expose the url where the request redirected to, in the `pw.response` object so it could be used in the scripts? https://docs.hoppscotch.io/documentation/features/scripts#pwresponse

kerem commented

2026-03-16 16:45:54 +03:00

Author

Owner

@KaKi87 commented on GitHub (Nov 10, 2023):

That's not an alternative because it wouldn't provide access to everything else the redirecting server returns (code, headers, even body), nor handle multiple redirections.

@KaKi87 commented on GitHub (Nov 10, 2023): That's not an alternative because it wouldn't provide access to everything else the redirecting server returns (code, headers, even body), nor handle multiple redirections.

kerem commented

2026-03-16 16:45:59 +03:00

Author

Owner

@Daanoz commented on GitHub (Nov 10, 2023):

True, it's not a full solution, but it might be something that can be more easily realized on a shorter timeframe.

In my usecase, I have an oAuth service with PKCE flow which I'm trying to validate. The oAuth spec defines one of the requests has to be a redirect, which includes a code token as parameter in the url. With the current client, there is simply no way to access that code value, not via the UI and not via scripting.

@Daanoz commented on GitHub (Nov 10, 2023): True, it's not a full solution, but it might be something that can be more easily realized on a shorter timeframe. In my usecase, I have an oAuth service with PKCE flow which I'm trying to validate. The oAuth spec defines one of the requests has to be a redirect, which includes a code token as parameter in the url. With the current client, there is simply no way to access that code value, not via the UI and not via scripting.

kerem commented

2026-03-16 16:46:04 +03:00

Author

Owner

@adilek commented on GitHub (Dec 13, 2023):

This feature is important for me and my team as well.

@adilek commented on GitHub (Dec 13, 2023): This feature is important for me and my team as well.

kerem commented

2026-03-16 16:46:09 +03:00

Author

Owner

@bttger commented on GitHub (Jan 1, 2024):

Why not simply add the redirect: "error" prop if users ask to disable redirects? I don't care about the location and status code. If really necessary I could just use another tool (e.g. httpie where redirects are always disabled). The fetch request would then just return TypeError: Failed to fetch. And either the user decides whether this has happened due to a redirect (since he/she disabled them intentionally) or hoppscotch does another request to test if the failure was due to the redirect (the response.redirected prop will be true). The latter would probably be preferred.

Here's how i tested it based on the MDN fetch redirect docs:

<!DOCTYPE html>
<html>
  <head>
    <title>Test Disabling Redirects</title>
  </head>
  <body>
    <h1>Test Disabling Redirects</h1>

    <script>
      window.addEventListener("load", function () {
        fetch(
          "http://raw.githubusercontent.com/bttger/wake-up-light/my-config/sunrise.json",
          { redirect: "error" }
        )
          .then((response) => {
            console.log(response);
            for (var pair of response.headers.entries()) {
              console.log(pair[0] + ": " + pair[1]);
            }
            return response.json();
          })
          .then((json) => console.log(json))
          .catch((error) => console.log(error));
      });
    </script>
  </body>
</html>

@bttger commented on GitHub (Jan 1, 2024): Why not simply add the `redirect: "error"` prop if users ask to disable redirects? I don't care about the location and status code. If really necessary I could just use another tool (e.g. httpie where redirects are always disabled). The fetch request would then just return `TypeError: Failed to fetch`. And either the user decides whether this has happened due to a redirect (since he/she disabled them intentionally) or hoppscotch does another request to test if the failure was due to the redirect (the `response.redirected` prop will be `true`). The latter would probably be preferred. Here's how i tested it based on the [MDN fetch redirect docs](https://developer.mozilla.org/en-US/docs/Web/API/Response/redirected): ```html <!DOCTYPE html> <html> <head> <title>Test Disabling Redirects</title> </head> <body> <h1>Test Disabling Redirects</h1> <script> window.addEventListener("load", function () { fetch( "http://raw.githubusercontent.com/bttger/wake-up-light/my-config/sunrise.json", { redirect: "error" } ) .then((response) => { console.log(response); for (var pair of response.headers.entries()) { console.log(pair[0] + ": " + pair[1]); } return response.json(); }) .then((json) => console.log(json)) .catch((error) => console.log(error)); }); </script> </body> </html> ```

kerem commented

2026-03-16 16:46:14 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jan 1, 2024):

I don't care about the location and status code.

I do.

@KaKi87 commented on GitHub (Jan 1, 2024): > I don't care about the location and status code. I do.

kerem commented

2026-03-16 16:46:19 +03:00

Author

Owner

@bttger commented on GitHub (Jan 2, 2024):

I do.

Then use another tool - it's not possible to get that info in a browser. But I showed a way how to disable redirects and to at least tell whether a redirect was responsible for the failure (if a request failed). I believe this would already help a lot.

@bttger commented on GitHub (Jan 2, 2024): > I do. Then use another tool - it's not possible to get that info in a browser. But I showed a way how to disable redirects and to at least tell whether a redirect was responsible for the failure (if a request failed). I believe this would already help a lot.

kerem commented

2026-03-16 16:46:24 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jan 2, 2024):

it's not possible to get that info in a browser

That's what the proxy and the desktop app are for.

@KaKi87 commented on GitHub (Jan 2, 2024): > it's not possible to get that info in a browser That's what the proxy and the desktop app are for.

kerem commented

2026-03-16 16:46:29 +03:00

Author

Owner

@bttger commented on GitHub (Jan 3, 2024):

That's what the proxy and the desktop app are for.

The proxy is a browser extension with the same limitation and the desktop app doesn't provide that feature either. What point do you want to make?

@bttger commented on GitHub (Jan 3, 2024): > That's what the proxy and the desktop app are for. The proxy is a browser extension with the same limitation and the desktop app doesn't provide that feature either. What point do you want to make?

kerem commented

2026-03-16 16:46:34 +03:00

Author

Owner

@KaKi87 commented on GitHub (Jan 4, 2024):

The proxy is a browser extension with the same limitation

No, the proxy is the proxy, and the browser extension is the browser extension.

Therefore, since not running in browser, the proxy could disable redirects.

the desktop app doesn't provide that feature either

Yes it does provide that feature, so it could disable redirects as well.

@KaKi87 commented on GitHub (Jan 4, 2024): > The proxy is a browser extension with the same limitation No, [the proxy is the proxy](https://github.com/hoppscotch/proxyscotch), and [the browser extension is the browser extension](https://github.com/hoppscotch/hoppscotch-extension). Therefore, since not running in browser, the proxy could disable redirects. > the desktop app doesn't provide that feature either Yes [it does provide that feature](https://tauri.app/v1/api/js/http/), so it could disable redirects as well.

kerem commented

2026-03-16 16:46:39 +03:00

Author

Owner

@bttger commented on GitHub (Jan 4, 2024):

Sorry, I didn't know there was an additional proxy. Had a quick look into it but personally I have no use case to use the proxy so I'd like to avoid the hassle (especially when working with WSL/docker and thinking that the USP of Hoppsotch is that I can just open the tool quickly on my work laptop without installing anything).

And yes, of course does Tauri support disabling of redirects but I was talking about the desktop app - it doesn't provide the disabling of redirects. And I still believe that my proposal would be a nice improvement over the current situation that would be easy to implement. Yes, it wouldn't show the status code but it would tell you that the request has failed due to a redirect.

@bttger commented on GitHub (Jan 4, 2024): Sorry, I didn't know there was an additional proxy. Had a quick look into it but personally I have no use case to use the proxy so I'd like to avoid the hassle (especially when working with WSL/docker and thinking that the USP of Hoppsotch is that I can just open the tool quickly on my work laptop without installing anything). And yes, of course does Tauri support disabling of redirects but I was talking about the desktop app - it doesn't provide the disabling of redirects. And I still believe that my proposal would be a nice improvement over the current situation that would be easy to implement. Yes, it wouldn't show the status code but it would tell you that the request has failed due to a redirect.

kerem commented

2026-03-16 16:46:44 +03:00

Author

Owner

@yannleretaille commented on GitHub (Nov 14, 2024):

Since the desktop app is using tauri now, shouldn't it be possible to add per-request option that sets curl::Easy::max_redirections to 0 in the native interceptor/relay?

I just hit the same issue testing an auth endpoint earlier, where I just needed to see the redirect status code, location headers etc. to confirm that it's working as intended and instead got a "Could not send request" error.

@yannleretaille commented on GitHub (Nov 14, 2024): Since the desktop app is using tauri now, shouldn't it be possible to add per-request option that sets [curl::Easy::max_redirections](https://docs.rs/curl/latest/curl/easy/struct.Easy.html#method.max_redirections) to `0` in the [native interceptor/relay](https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-relay/src/relay.rs)? I just hit the same issue testing an auth endpoint earlier, where I just needed to see the redirect status code, location headers etc. to confirm that it's working as intended and instead got a "Could not send request" error.

kerem commented

2026-03-16 16:46:50 +03:00

Author

Owner

@macmessa commented on GitHub (Aug 26, 2025):

Is this in the backlog?

@macmessa commented on GitHub (Aug 26, 2025): Is this in the backlog?

kerem commented

2026-03-16 16:46:55 +03:00

Author

Owner

@carlos-dubon commented on GitHub (Oct 11, 2025):

i have the opposite problem. i want to enable them, but i cant find the toggle

@carlos-dubon commented on GitHub (Oct 11, 2025): i have the opposite problem. i want to enable them, but i cant find the toggle

kerem commented

2026-03-16 16:47:00 +03:00

Author

Owner

@KaKi87 commented on GitHub (Oct 12, 2025):

i want to enable them

The reason why this issue is a feature request for disabling redirects is that redirects are enabled by default and cannot be disabled.

@KaKi87 commented on GitHub (Oct 12, 2025): > i want to enable them The reason why this issue is a feature request for disabling redirects is that redirects are enabled by default and cannot be disabled.

kerem commented

2026-03-16 16:47:05 +03:00

Author

Owner

@carlos-dubon commented on GitHub (Oct 12, 2025):

i want to enable them

The reason why this issue is a feature request for disabling redirects is that redirects are enabled by default and cannot be disabled.

Yeah I'm not trying to be odd or something. It's just that mine isn't redirecting. Maybe I'll open another issue

@carlos-dubon commented on GitHub (Oct 12, 2025): > > i want to enable them > > The reason why this issue is a feature request for disabling redirects is that redirects are enabled by default and cannot be disabled. Yeah I'm not trying to be odd or something. It's just that mine isn't redirecting. Maybe I'll open another issue

kerem commented

2026-03-16 16:47:10 +03:00

Author

Owner

@KaKi87 commented on GitHub (Oct 12, 2025):

Okay, though that's likely an issue on your API, I'm afraid. I'd suggest getting raw output using cURL, feeding it to an AI, along with the redirect you expected, and asking it why it doesn't.

@KaKi87 commented on GitHub (Oct 12, 2025): Okay, though that's likely an issue on your API, I'm afraid. I'd suggest getting raw output using cURL, feeding it to an AI, along with the redirect you expected, and asking it why it doesn't.

kerem commented

2026-03-16 16:47:15 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Oct 31, 2025):

Hi, the ability to disable redirects has been added to the Desktop App and Agent micro application for use in the web app as part of the latest release. Please feel free to share any feedback.

@jamesgeorge007 commented on GitHub (Oct 31, 2025): Hi, the ability to disable redirects has been added to the Desktop App and [Agent](https://docs.hoppscotch.io/documentation/features/interceptor#hoppscotch-agent) micro application for use in the web app as part of the [latest release](https://github.com/hoppscotch/hoppscotch/releases/tag/2025.10.0). Please feel free to share any feedback. <img width="1494" height="435" alt="Image" src="https://github.com/user-attachments/assets/00cddcdd-976c-4614-9eed-9c88a122dba2" /> <img width="1476" height="680" alt="Image" src="https://github.com/user-attachments/assets/2b89383f-f38a-4bf1-b077-33aee0adc125" />

Rows
Columns

[GH-ISSUE #2095] [feature]: Disable redirects #699

Is there an existing issue for this?

Summary

Why should this be worked on?