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.

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

IIS Reverse Proxy Settings: Pull Requests require additional Parameter #16245

Closed
2 of 8 tasks
nexero opened this issue Jun 25, 2021 · 0 comments · Fixed by #16246
Closed
2 of 8 tasks

IIS Reverse Proxy Settings: Pull Requests require additional Parameter #16245

nexero opened this issue Jun 25, 2021 · 0 comments · Fixed by #16246

Comments

@nexero
Copy link
Contributor

nexero commented Jun 25, 2021

  • Gitea version (or commit ref): 1.14.3 built with GNU Make 4.1, go1.16.5 : bindata, sqlite, sqlite_unlock_notify
  • Git version: 2.32.0
  • Operating system:
    • Microsoft Windows Server 2019 \w IIS reverse proxy configuration
    • pre-built .exe
    • Windows Service
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MariaDB
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When trying to setup Gitea on a Windows Server 2019 with IIS using the reverse proxy configuration example from the official documentation, pull requests won't work at all. Server is returning 400.

This is due to some weird IIS specifics, they don't allow to use some special characters in the URL by default.

Fix

Adding this to the config fixes the pull requests:

<system.web>
    <httpRuntime requestPathInvalidCharacters="" />
</system.web>

I'll create a pull request for this issue.

nexero added a commit to nexero/gitea that referenced this issue Jun 25, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant