Fossil SCM

cgi.md: be less specific about the Apache version in which the Content-Length change happened because a new forum post reports that it happens at least as far back as 2.4.41.

stephan 2024-04-22 16:29 trunk
Commit 9af5f38671295d6d4283ae6fefc5bfd316f3c69ca1d6530a39993945112fd016
1 file changed +2 -2
--- www/server/any/cgi.md
+++ www/server/any/cgi.md
@@ -91,12 +91,12 @@
9191
9292
*[Return to the top-level Fossil server article.](../)*
9393
9494
#### Apache mod_cgi and `CONTENT_LENGTH`
9595
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.
96
+At some point in its 2.4.x family, Apache's `mod_cgi` stopped relaying
97
+the Content-Length header in the HTTP reply from CGIs back to clients.
9898
However, Fossil clients prior to 2024-04-17 depended on seeing the
9999
Content-Length header and were unable to handle HTTP replies without
100100
one. The change in Apache behavior caused "fossil clone" and "fossil
101101
sync" to stop working. There are two possible fixes to this problem:
102102
103103
--- www/server/any/cgi.md
+++ www/server/any/cgi.md
@@ -91,12 +91,12 @@
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
--- www/server/any/cgi.md
+++ www/server/any/cgi.md
@@ -91,12 +91,12 @@
91
92 *[Return to the top-level Fossil server article.](../)*
93
94 #### Apache mod_cgi and `CONTENT_LENGTH`
95
96 At some point in its 2.4.x family, Apache's `mod_cgi` stopped relaying
97 the 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

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button