Skip to content

OAuth POST routes not using base path #8466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks
h3kker opened this issue Oct 11, 2019 · 1 comment
Closed
5 tasks

OAuth POST routes not using base path #8466

h3kker opened this issue Oct 11, 2019 · 1 comment

Comments

@h3kker
Copy link

h3kker commented Oct 11, 2019

  • Gitea version (or commit ref): 1.9.4
  • Git version: 2.22.0
  • Operating system: alpine 3.10.2
  • Database (use [x]):
    • [ x] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [x ] Not relevant
  • Log gist:

Description

We have a gitea installation (docker) behind a reverse proxy, accessible under a subpath, like https://example.com/repo/ (setting ROOT_URL = https://example.com/repo/)

This works well, but recently I tried to use an OAuth application (drone). I get the redirect to the gitea server to https://example.com/repo/login/oauth/authorize, but when I do click the "Authorize Application" button, the POST request goes to the base URL (without /repo) instead: https://example.com/login/oauth/authorize.

The same thing happens in the settings on the configuration page https://example.com/repo/user/settings/applications/oauth2/1
Clicking on the Save button sends the POST request to http://example.com/user/settings/applications/oauth2/1

I could not see any configuration settings (besides ROOT_URL) where I could set this up, but maybe I've missed something - in that case I'm sorry (and grateful for a pointer).

Thanks,
Heinz

@h3kker
Copy link
Author

h3kker commented Oct 15, 2019

sorry, duplicate of #8461 opened just hours before I did...

@h3kker h3kker closed this as completed Oct 15, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant