mirror of https://github.com/go-gitea/gitea.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2f2ca8c940
See [issue on gitea.com](https://gitea.com/gitea/gitea-docusaurus/issues/38), copied below for convenience: > Hello, may I first confirm that the app.ini PROTOCOL config is case sensitive (must be lowercase)? > > If so, I'd like to suggest for it to be highlighted in the [HTTPS Setup](https://docs.gitea.com/administration/https-setup#using-the-built-in-server) page. > Perhaps something like: > For the PROTOCOL=https field, make sure https is lowercase. Writing PROTOCOL=HTTPS may result in a SSL_ERROR_RX_RECORD_TOO_LONG error on Firefox or ERR_SSL_PROTOCOL_ERROR on Chrome and Edge. > > Background > At first I carelessly wrote PROTOCOL=HTTPS in my app.ini, and Firefox didn't allow me to connect because: > Secure Connection Failed > An error occurred during a connection to gitea.local.lan. SSL received a record that exceeded the maximum permissible length. > Error code: SSL_ERROR_RX_RECORD_TOO_LONG > I spent maybe half an hour troubleshooting my certs, ports, and other configs before backtracking to the start and realizing the capitalization difference there 😅. When I changed that config to lowercase, it worked. For this PR I added the note in the Config Cheat Sheet page and fixed the links to it from the HTTPS Setup page. Was originally thinking to put the note in the HTTPS Setup page itself, but since there are 2 sections referencing the PROTOCOL config, I was thinking it'd be neater and more concise to put it in the Config Cheat Sheet page instead. Especially since both sections already link to it, and I actually tried to check that link quite early on in my troubleshooting (but didn't pay much attention to it since the link was broken). ## Before/After screenshots as per [this repo's docs](https://github.com/go-gitea/gitea/tree/main/docs) Before - links  Note: For this the links weren't broken, the links fix is because they were broken on gitea.com's docs (see below). After - links  Before - config cheat sheet  After - config cheat sheet  ## Before/After screenshots as per [gitea.com's docs](https://gitea.com/gitea/gitea-docusaurus) Before - links  After - links  Before - config cheat sheet  After - config cheat sheet  |
1 year ago | |
|---|---|---|
| .. | ||
| _index.en-us.md | 2 years ago | |
| _index.zh-cn.md | 2 years ago | |
| adding-legal-pages.en-us.md | 2 years ago | |
| adding-legal-pages.zh-cn.md | 2 years ago | |
| backup-and-restore.en-us.md | 1 year ago | |
| backup-and-restore.zh-cn.md | 2 years ago | |
| cmd-embedded.en-us.md | 1 year ago | |
| cmd-embedded.zh-cn.md | 1 year ago | |
| command-line.en-us.md | 1 year ago | |
| command-line.zh-cn.md | 1 year ago | |
| config-cheat-sheet.en-us.md | 1 year ago | |
| config-cheat-sheet.zh-cn.md | 1 year ago | |
| customizing-gitea.en-us.md | 1 year ago | |
| customizing-gitea.zh-cn.md | 1 year ago | |
| email-setup.en-us.md | 2 years ago | |
| email-setup.zh-cn.md | 2 years ago | |
| environment-variables.en-us.md | 2 years ago | |
| environment-variables.zh-cn.md | 2 years ago | |
| external-renderers.en-us.md | 1 year ago | |
| external-renderers.zh-cn.md | 2 years ago | |
| fail2ban-setup.en-us.md | 1 year ago | |
| fail2ban-setup.zh-cn.md | 1 year ago | |
| git-lfs-support.en-us.md | 2 years ago | |
| git-lfs-support.zh-cn.md | 2 years ago | |
| https-support.en-us.md | 1 year ago | |
| https-support.zh-cn.md | 1 year ago | |
| logging-config.en-us.md | 2 years ago | |
| logging-config.zh-cn.md | 2 years ago | |
| mail-templates.en-us.md | 1 year ago | |
| mail-templates.zh-cn.md | 1 year ago | |
| repo-indexer.en-us.md | 1 year ago | |
| repo-indexer.zh-cn.md | 1 year ago | |
| reverse-proxies.en-us.md | 1 year ago | |
| reverse-proxies.zh-cn.md | 2 years ago | |
| search-engines-indexation.en-us.md | 1 year ago | |
| search-engines-indexation.zh-cn.md | 1 year ago | |
| signing.en-us.md | 2 years ago | |
| signing.zh-cn.md | 2 years ago | |