github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

URL Composition Problems with Alternative Port Configurations #1004

New Issue
Closed
opened 2025-11-02 03:44:57 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-02 03:44:57 -06:00
Owner
Copy Link

Originally created by @smeddinck on GitHub (Aug 26, 2017).

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

Description

I use an alternative port for gitea via ssl (on nginx). Many API related links (e.g. https://mysite.com/swagger.v1.json or slack integration backlinks) miss the port (since it should be https://mysite.com:4242/swagger.v1.json). Gitea 1.2 on Debian 8 with MySQL

Originally created by @smeddinck on GitHub (Aug 26, 2017). - Gitea version (or commit ref): 1.2 - Git version: - Operating system: Debian 8 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [x] Not relevant - Log gist: ## Description I use an alternative port for gitea via ssl (on nginx). Many API related links (e.g. https://mysite.com/swagger.v1.json or slack integration backlinks) miss the port (since it should be https://mysite.com:4242/swagger.v1.json). Gitea 1.2 on Debian 8 with MySQL
GiteaMirror added the type/bug label 2025-11-02 03:44:57 -06:00
GiteaMirror commented 2025-11-02 03:44:58 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Nov 26, 2017):

It's the same for https://mysite.com/mypath/swagger.v1.json. It looks like ROOT_URL is not being prepended to Swagger's basePath. Unfortunately this makes Gitea's Swagger documentation unusable with custom root URLs.

@0rzech commented on GitHub (Nov 26, 2017): It's the same for `https://mysite.com/mypath/swagger.v1.json`. It looks like [`ROOT_URL`](/go-gitea/gitea/blob/v1.2.3/conf/app.ini#L100) is not being prepended to Swagger's [`basePath`](/go-gitea/gitea/blob/v1.2.3/public/swagger.v1.json#L25). Unfortunately this makes Gitea's Swagger documentation unusable with custom root URLs.
GiteaMirror commented 2025-11-02 03:44:58 -06:00
Author
Owner
Copy Link

@igsol commented on GitHub (Aug 6, 2018):

I have a similar problem. My Gitea server runs behind SSL reverse proxy which makes not default URL to Gitea service, e.g. https://example.com/gitea/.
But Swagger page continues to use https://example.com/api/v1/ with missed "gitea" part after hostname.

@igsol commented on GitHub (Aug 6, 2018): I have a similar problem. My Gitea server runs behind SSL reverse proxy which makes not default URL to Gitea service, e.g. https://example.com/**gitea**/. But Swagger page continues to use https://example.com/api/v1/ with missed "gitea" part after hostname.
GiteaMirror commented 2025-11-02 03:44:58 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Aug 7, 2018):

@igsol This should be fixed in #3572.

@0rzech commented on GitHub (Aug 7, 2018): @igsol This should be fixed in #3572.
GiteaMirror commented 2025-11-02 03:44:58 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Aug 8, 2018):

@lunny Mine and @igsol's case is solved, but I am not sure about @smeddinck's, as it seems to be a different kind of bug with different solution.

@0rzech commented on GitHub (Aug 8, 2018): @lunny Mine and @igsol's case is solved, but I am not sure about @smeddinck's, as it seems to be a different kind of bug with different solution.
GiteaMirror commented 2025-11-02 03:44:58 -06:00
Author
Owner
Copy Link

@igsol commented on GitHub (Aug 8, 2018):

@0rzech Thanks! I am on v1.4.3 still. Waiting for next release :)

@igsol commented on GitHub (Aug 8, 2018): @0rzech Thanks! I am on v1.4.3 still. Waiting for next release :)
GiteaMirror commented 2025-11-02 03:44:59 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Aug 8, 2018):

@igsol You're welcome. ;)

@0rzech commented on GitHub (Aug 8, 2018): @igsol You're welcome. ;)
GiteaMirror commented 2025-11-02 03:44:59 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 8, 2018):

@smeddinck could you confirm #3572 resolved your issue?

@lunny commented on GitHub (Aug 8, 2018): @smeddinck could you confirm #3572 resolved your issue?
GiteaMirror commented 2025-11-02 03:44:59 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Aug 8, 2018):

@igsol I forgot to remind you the fix will be available in 1.6 version, not in 1.5.

@0rzech commented on GitHub (Aug 8, 2018): @igsol I forgot to remind you the fix will be available in 1.6 version, not in 1.5.
GiteaMirror commented 2025-11-02 03:44:59 -06:00
Author
Owner
Copy Link

@igsol commented on GitHub (Aug 8, 2018):

@0rzech NP, it's not urgent. The bug actually is not so critical as for me, cause it makes Swagger UI usage a bit harder, but API itself works flawlessly :)

@igsol commented on GitHub (Aug 8, 2018): @0rzech NP, it's not urgent. The bug actually is not so critical as for me, cause it makes Swagger UI usage a bit harder, but API itself works flawlessly :)
GiteaMirror commented 2025-11-02 03:44:59 -06:00
Author
Owner
Copy Link

@0rzech commented on GitHub (Aug 8, 2018):

@igsol Sure thing! Just wanted to avoid potential confusion. ;)

@0rzech commented on GitHub (Aug 8, 2018): @igsol Sure thing! Just wanted to avoid potential confusion. ;)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1004
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?