Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wrong content type for orgEditTeam #3843

Closed
2 of 7 tasks
nblock opened this issue Apr 23, 2018 · 2 comments
Closed
2 of 7 tasks

Wrong content type for orgEditTeam #3843

nblock opened this issue Apr 23, 2018 · 2 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug type/docs This PR mainly updates/creates documentation

Comments

@nblock
Copy link

nblock commented Apr 23, 2018

  • Gitea version 1.3.3
  • Git version: 2.11.0
  • Operating system: Debian Stretch
  • 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

The swagger documentation for https://try.gitea.io/api/swagger#/organization/orgEditTeam specifies the content type as application/json while only form data works.

Extracted from #3600
@lunny lunny added type/bug type/docs This PR mainly updates/creates documentation labels Apr 24, 2018
@kainz kainz mentioned this issue Jun 25, 2018
Closed
6 tasks
@stale stale bot added the issue/stale label Jan 28, 2019
@techknowlogick techknowlogick added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jan 28, 2019
@go-gitea go-gitea deleted a comment from stale bot Jan 28, 2019
@6543
Copy link
Member

6543 commented Dec 31, 2019

@nblock I can't reproduce it!

maby you got into this trap: #9556

can you try it again and if it works close this issue?

@nblock
Copy link
Author

nblock commented Dec 31, 2019

@6543 I no longer have access to the code and tooling mentioned in the bug report. Therefore, I rather close this issue.

@nblock nblock closed this as completed Dec 31, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug type/docs This PR mainly updates/creates documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @nblock @techknowlogick @6543