You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
URL Composition Problems with Alternative Port Configurations #2403
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.
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.
@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 :)
Activity
0rzech commentedon Nov 26, 2017
It's the same for
https://mysite.com/mypath/swagger.v1.json. It looks likeROOT_URLis not being prepended to Swagger'sbasePath. Unfortunately this makes Gitea's Swagger documentation unusable with custom root URLs.igsol commentedon 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.
0rzech commentedon Aug 7, 2018
@igsol This should be fixed in #3572.
0rzech commentedon 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.
igsol commentedon Aug 8, 2018
@0rzech Thanks! I am on v1.4.3 still. Waiting for next release :)
0rzech commentedon Aug 8, 2018
@igsol You're welcome. ;)
lunny commentedon Aug 8, 2018
@smeddinck could you confirm #3572 resolved your issue?
0rzech commentedon Aug 8, 2018
@igsol I forgot to remind you the fix will be available in 1.6 version, not in 1.5.
igsol commentedon 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 :)
0rzech commentedon Aug 8, 2018
@igsol Sure thing! Just wanted to avoid potential confusion. ;)