mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3764] [feature]: Better support for localhost testing with Proxy enabled #1311
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#1311
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 @Leon-Luu on GitHub (Jan 19, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3764
Originally assigned to: @AndrewBastin on GitHub.
Is there an existing issue for this?
Summary
When Proxy middleware is enabled, it is not able to send enpoints with localhost resulting a window with "Could not send request". The users has to choose "None" or "Browser extension" to be able to send to the localhost.

The feature request is Hoppscotch to automatic detect this and temporary disable the Proxy for allowing testing on localhost with the Proxy enabled. Users shall not need disable the Proxy settings and enable again.
Why should this be worked on?
@liyasthomas commented on GitHub (Jan 19, 2024):
Can you try our alpha release candidate for desktop app let us know.
https://hoppscotch.com/download
@Leon-Luu commented on GitHub (Jan 19, 2024):
@liyasthomas It is the same for "alpha release candidate desktop" one, not able to send on localhost without choosing to native
@liyasthomas commented on GitHub (Jan 19, 2024):
This is an expected behaviour. You should set the interceptor to Native on desktop app or Browser Extension on web app.
I'd recommend you to use desktop app with Native interceptor since it support both locally hosted and deployed APIs.
@AllenAttuned commented on GitHub (Feb 6, 2024):
A somewhat related issue I have is with requests to local endpoints which have hostnames (ie: mappings defined in
/etc/hosts). Our setup needs requires hostnames for SSL, so we use Nginx to reverse proxy our requests to the respected services. It works in the browser (or PWA) with the extension, but it would be nice if it also worked natively, especially since cookie support is limited to the native application.@ash-eng-spin commented on GitHub (Feb 15, 2024):
So on the desktop version, to test a request running on localhost, you should be able to have Native interceptor selected and it should run?
I'm on Windows v2023.12.4 and I have a simple GET request to an API running on localhost. Native Interceptor selected. I get "Could not send request".
@AndrewBastin commented on GitHub (Feb 16, 2024):
@ash-eng-spin if you are running into this issue, please do open a new issue for this as it is unrelated to the issue mentioned here along with some steps for reproduction if possible.
@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.