mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3768] [feature]: proxy support #1313
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#1313
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 @baek-sang on GitHub (Jan 22, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3768
Is there an existing issue for this?
Summary
Need
socks,http,httpsproxy supportnot proxyscotch
Why should this be worked on?
To work in an internal network
@danielloader commented on GitHub (Jan 30, 2024):
SOCKS5 proxy would be very useful when paired with mirrord (via microsocks) for executing http requests inside of a target Kubernetes cluster.
@billy-doyle commented on GitHub (Sep 1, 2024):
something like this equivalent curl command for proxies would be perfect:
curl -X GET --proxy 'http://some-squid-proxy:3128' 'https://api.example.com/v1/endpoint'@Jellayy commented on GitHub (Sep 9, 2024):
+1
Not being able to utilize a simple HTTP proxy on localhost in the proxy interceptor makes this completely unusable in a corporate environment. This is a feature in other platforms like postman and insomnia and some even respect the
HTTP_PROXYHTTPS_PROXYandNO_PROXYvars in your environment which is super helpful.@liyasthomas commented on GitHub (Sep 25, 2024):
Reopening this issue for continued tracking as it was unintentionally closed. This is still relevant for further discussion/implementation. Thank you!