Skip to content

URL Composition Problems with Alternative Port Configurations #2403

Closed

Description

@smeddinck
  • 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

Activity

  1. 0rzech commented on Nov 26, 2017

    @0rzech
    Contributor

    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.

  2. igsol commented on Aug 6, 2018

    @igsol

    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.

  3. 0rzech commented on Aug 7, 2018

    @0rzech
    Contributor

    @igsol This should be fixed in #3572.

  4. added this to the 1.6.0 milestone on Aug 8, 2018
  5. 0rzech commented on Aug 8, 2018

    @0rzech
    Contributor

    @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.

  6. igsol commented on Aug 8, 2018

    @igsol

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

  7. 0rzech commented on Aug 8, 2018

    @0rzech
    Contributor

    @igsol You're welcome. ;)

  8. lunny commented on Aug 8, 2018

    @lunny
    Member

    @smeddinck could you confirm #3572 resolved your issue?

  9. 0rzech commented on Aug 8, 2018

    @0rzech
    Contributor

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

  10. igsol commented on Aug 8, 2018

    @igsol

    @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 :)

  11. 0rzech commented on Aug 8, 2018

    @0rzech
    Contributor

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

  12. locked and limited conversation to collaborators on Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions