mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #1009] postwoman google login doesn't work behind ingress or reverse proxy #350
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#350
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 @ghost on GitHub (Jul 21, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1009
Describe the bug
Google login doesn't work when you deploy postwoman behind reverse proxy or ingress
To Reproduce
Steps to reproduce the behavior:
Easiest way to reproduce is run below docker-compose and login to google by http://localhost:80 (reverse_proxy) instead of http://localhost:3000 (postwoman direct)
https://gist.github.com/javad-hajiani/c604f42e3fc0068ae65b482a3adf8278
Expected behavior
google login work properly like what you have already without reverse_proxy
Desktop (please complete the following information):
@liyasthomas commented on GitHub (Jul 21, 2020):
Login is disabled for all request URLs except
postwoman.iodue to security concerns. Kindly use postwoman.io to make use of sync feature.Duplicate of #817
@schndr commented on GitHub (Jul 21, 2020):
@liyasthomas Can you please elaborate the security concerns in detail?