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

API explorer assumes HTTP, breaks curl. #1186

New Issue
Closed
opened 2025-11-02 03:51:46 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 03:51:46 -06:00
Owner
Copy Link

Originally created by @issmirnov on GitHub (Oct 27, 2017).

  • Gitea version (or commit ref): 1.2.2
  • Git version: 2.7.4
  • Operating system: Ubuntu 16.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:

Description

When I use the API explorer (lives on /swagger) I am unable to execute commands. Looking at the generated curl command, I see that it starts with http and not https. Since the curl command doesn't have the follow redirects flag (-L) the command fails.

Error: TypeError: Failed to fetch

Screenshots

image 2017-10-26 at 22 26 11

Originally created by @issmirnov on GitHub (Oct 27, 2017). - Gitea version (or commit ref): 1.2.2 - Git version: 2.7.4 - Operating system: Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - https://try.gitea.io/swagger send me to a user page, not API explorer. - [ ] Not relevant ## Description When I use the API explorer (lives on `/swagger`) I am unable to execute commands. Looking at the generated curl command, I see that it starts with `http` and not `https`. Since the curl command doesn't have the follow redirects flag (`-L`) the command fails. Error: `TypeError: Failed to fetch` ## Screenshots ![image 2017-10-26 at 22 26 11](https://user-images.githubusercontent.com/5771615/32089074-b9ee48d8-ba9c-11e7-8106-11dd07fe327d.png)
GiteaMirror added the type/docs label 2025-11-02 03:51:46 -06:00
GiteaMirror commented 2025-11-02 03:51:47 -06:00
Author
Owner
Copy Link

@issmirnov commented on GitHub (Oct 27, 2017):

FWIW, Application URL = https://git.smirnov.work, so the HTTPS is there.

@issmirnov commented on GitHub (Oct 27, 2017): FWIW, `Application URL = https://git.smirnov.work`, so the HTTPS is there.
GiteaMirror commented 2025-11-02 03:51:47 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Oct 30, 2017):

This is a problem of swagger UI. Please simply select HTTPS as schema if you only use HTTPS. (See screenshot). This can't be removed since some users allow HTTP traffic without redirection. And swagger ui could (not yet) determine if HTTPS is redirected or not.
HTTPS Schema

@jonasfranz commented on GitHub (Oct 30, 2017): This is a problem of swagger UI. Please simply select HTTPS as schema if you only use HTTPS. (See screenshot). This can't be removed since some users allow HTTP traffic without redirection. And swagger ui could (not yet) determine if HTTPS is redirected or not. ![HTTPS Schema](https://user-images.githubusercontent.com/5757182/32176517-3199d152-bd88-11e7-9d6a-3ec4be4dd9c3.png)
GiteaMirror commented 2025-11-02 03:51:47 -06:00
Author
Owner
Copy Link

@issmirnov commented on GitHub (Nov 3, 2017):

Understood, thanks!

@issmirnov commented on GitHub (Nov 3, 2017): Understood, thanks!
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/docs
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#1186
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?