Swagger "try it out" not working in prefixed Gitea instance running https #2693

Closed
opened 2025-11-02 04:44:40 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @OndrejSpanel on GitHub (Dec 27, 2018).

Followup to #3499 and #4907

  • Gitea version (or commit ref): 1.6.2
  • Git version: 1.9.1
  • Operating system: Debian 7
  • 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 am serving my gitea on URL like https://www.myserver.net/gitea, configured using Apache reverse proxy mapping this URL to http://localhost:3000. Main reason for this is my current SSL certificate does not allow subdomains. Everything works fine, the only problem I have is with Swagger.

The URL used for requests is almost fine, but requests are using plain insecure http:// prefx, while the instance is available using secure https:// one.

Screenshots

image

image

Originally created by @OndrejSpanel on GitHub (Dec 27, 2018). _Followup to #3499 and #4907_ - Gitea version (or commit ref): 1.6.2 - Git version: 1.9.1 - Operating system: Debian 7 - 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 am serving my gitea on URL like https://www.myserver.net/gitea, configured using Apache reverse proxy mapping this URL to http://localhost:3000. Main reason for this is my current SSL certificate does not allow subdomains. Everything works fine, the only problem I have is with Swagger. The URL used for requests is almost fine, but requests are using plain insecure `http://` prefx, while the instance is available using secure `https://` one. ## Screenshots ![image](https://user-images.githubusercontent.com/6927223/50483697-37d33b00-09ed-11e9-8e44-ce1657507527.png) ![image](https://user-images.githubusercontent.com/6927223/50483668-1ffbb700-09ed-11e9-9b90-a3bb0faf60b2.png)
Author
Owner

@OndrejSpanel commented on GitHub (Dec 27, 2018):

I see now I need to choose http / https explicitelly on top of the swagger page. The behaviour could perhaps be more intuitive, but given this is developer only page, I think it is not worth any effort.

Closing as PEBCAK

@OndrejSpanel commented on GitHub (Dec 27, 2018): I see now I need to choose http / https explicitelly on top of the swagger page. The behaviour could perhaps be more intuitive, but given this is developer only page, I think it is not worth any effort. Closing as PEBCAK
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2693