Fossil SCM
Typo fix and add specific Apache version number to the notes about the Content-Length change.
Commit
d0f4288916b4b309ef67ff9a534b74df520d93d79e9d6627c2e5a62d0bc96c34
Parent
8b805013e26b2b4…
1 file changed
+4
-4
+4
-4
| --- www/server/any/cgi.md | ||
| +++ www/server/any/cgi.md | ||
| @@ -91,16 +91,16 @@ | ||
| 91 | 91 | |
| 92 | 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 | 93 | |
| 94 | 94 | #### Apache mod_cgi and `CONTENT_LENGTH` |
| 95 | 95 | |
| 96 | -Sometime around version 2.4, Apache's `mod_cgi` stopped relaying the | |
| 96 | +In version 2.4.59, Apache's `mod_cgi` stopped relaying the | |
| 97 | 97 | Content-Length header in the HTTP reply from CGIs back to clients. |
| 98 | -However, Fossil clients prior to 2024-04-17 depending on seeing the | |
| 98 | +However, Fossil clients prior to 2024-04-17 depended on seeing the | |
| 99 | 99 | Content-Length header and were unable to handle HTTP replies without |
| 100 | -one. The change in Apache behavior caused "fossil clone" and "fossil sync" | |
| 101 | -to stop working. There are two possible fixes to this problem: | |
| 100 | +one. The change in Apache behavior caused "fossil clone" and "fossil | |
| 101 | +sync" to stop working. There are two possible fixes to this problem: | |
| 102 | 102 | |
| 103 | 103 | 1. Restore legacy behavior in Apache by adding |
| 104 | 104 | the following to the Apache configuration, scoped to the `<Directory>` |
| 105 | 105 | entry or entries in which fossil is being served via CGI: |
| 106 | 106 | <blockquote><pre> |
| 107 | 107 |
| --- www/server/any/cgi.md | |
| +++ www/server/any/cgi.md | |
| @@ -91,16 +91,16 @@ | |
| 91 | |
| 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 | |
| 94 | #### Apache mod_cgi and `CONTENT_LENGTH` |
| 95 | |
| 96 | Sometime around version 2.4, Apache's `mod_cgi` stopped relaying the |
| 97 | Content-Length header in the HTTP reply from CGIs back to clients. |
| 98 | However, Fossil clients prior to 2024-04-17 depending on seeing the |
| 99 | Content-Length header and were unable to handle HTTP replies without |
| 100 | one. The change in Apache behavior caused "fossil clone" and "fossil sync" |
| 101 | to stop working. There are two possible fixes to this problem: |
| 102 | |
| 103 | 1. Restore legacy behavior in Apache by adding |
| 104 | the following to the Apache configuration, scoped to the `<Directory>` |
| 105 | entry or entries in which fossil is being served via CGI: |
| 106 | <blockquote><pre> |
| 107 |
| --- www/server/any/cgi.md | |
| +++ www/server/any/cgi.md | |
| @@ -91,16 +91,16 @@ | |
| 91 | |
| 92 | *[Return to the top-level Fossil server article.](../)* |
| 93 | |
| 94 | #### Apache mod_cgi and `CONTENT_LENGTH` |
| 95 | |
| 96 | In version 2.4.59, Apache's `mod_cgi` stopped relaying the |
| 97 | Content-Length header in the HTTP reply from CGIs back to clients. |
| 98 | However, Fossil clients prior to 2024-04-17 depended on seeing the |
| 99 | Content-Length header and were unable to handle HTTP replies without |
| 100 | one. The change in Apache behavior caused "fossil clone" and "fossil |
| 101 | sync" to stop working. There are two possible fixes to this problem: |
| 102 | |
| 103 | 1. Restore legacy behavior in Apache by adding |
| 104 | the following to the Apache configuration, scoped to the `<Directory>` |
| 105 | entry or entries in which fossil is being served via CGI: |
| 106 | <blockquote><pre> |
| 107 |