Fossil SCM
Add a note about how to work around the Apache mod_cgi CONTENT_LENGTH behavior change which breaks fossil sync, as covered in [forum:12ac403fd29cfc89|forum post 12ac403fd29cfc89].
Commit
586dc75f498f231ab4da58d7374f2e881bc481feb61e48f1547753651a1fece6
Parent
6a571f88ccf5ef5…
1 file changed
+14
+14
| --- www/server/any/cgi.md | ||
| +++ www/server/any/cgi.md | ||
| @@ -88,5 +88,19 @@ | ||
| 88 | 88 | proxy_set_header X-Forwarded-Proto $scheme; |
| 89 | 89 | |
| 90 | 90 | has been be added in the relevant proxying section of the Nginx config file. |
| 91 | 91 | |
| 92 | 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 | + | |
| 94 | +#### Apache mod_cgi and `CONTENT_LENGTH` | |
| 95 | + | |
| 96 | +Sometime in version 2.4, Apache's `mod_cgi` stopped passing on the | |
| 97 | +`CONTENT_LENGTH` CGI variable to clients, which breaks fossil's sync | |
| 98 | +protocol. In order to restore that functionality, clients need to add | |
| 99 | +the following to their Apache configuration, scoped to the `<Directory>` | |
| 100 | +entry or entries in which fossil is being served via CGI: | |
| 101 | + | |
| 102 | +``` | |
| 103 | +<Directory ...> | |
| 104 | + SetEnv ap_trust_cgilike_cl "yes" | |
| 105 | +</Directory> | |
| 106 | +``` | |
| 93 | 107 |
| --- www/server/any/cgi.md | |
| +++ www/server/any/cgi.md | |
| @@ -88,5 +88,19 @@ | |
| 88 | proxy_set_header X-Forwarded-Proto $scheme; |
| 89 | |
| 90 | has been be added in the relevant proxying section of the Nginx config file. |
| 91 | |
| 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 |
| --- www/server/any/cgi.md | |
| +++ www/server/any/cgi.md | |
| @@ -88,5 +88,19 @@ | |
| 88 | proxy_set_header X-Forwarded-Proto $scheme; |
| 89 | |
| 90 | has been be added in the relevant proxying section of the Nginx config file. |
| 91 | |
| 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 | |
| 94 | #### Apache mod_cgi and `CONTENT_LENGTH` |
| 95 | |
| 96 | Sometime in version 2.4, Apache's `mod_cgi` stopped passing on the |
| 97 | `CONTENT_LENGTH` CGI variable to clients, which breaks fossil's sync |
| 98 | protocol. In order to restore that functionality, clients need to add |
| 99 | the following to their Apache configuration, scoped to the `<Directory>` |
| 100 | entry or entries in which fossil is being served via CGI: |
| 101 | |
| 102 | ``` |
| 103 | <Directory ...> |
| 104 | SetEnv ap_trust_cgilike_cl "yes" |
| 105 | </Directory> |
| 106 | ``` |
| 107 |