summaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authorRyan Bloom <rbb@apache.org>2001-04-16 23:16:53 +0200
committerRyan Bloom <rbb@apache.org>2001-04-16 23:16:53 +0200
commita7bc1f3efab54aea6e413330f1cd317f2fad3550 (patch)
treecc7870c0cb13e30e49ebb65740ee47e630e6ba38 /CHANGES
parentSilly typo. (diff)
downloadapache2-a7bc1f3efab54aea6e413330f1cd317f2fad3550.tar.xz
apache2-a7bc1f3efab54aea6e413330f1cd317f2fad3550.zip
If a higher-level filter handles the the byterange aspects of a
request, then the byterange filter should not try to redo the work. The most common case of this happening, is a byterange request going through the proxy, and the origin server handles the byterange request. The proxy should ignore it. Submitted by: Graham Leggett <minfrin@sharp.fm> git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88873 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES7
1 files changed, 7 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 8786951866..cc58874a1a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,5 +1,12 @@
Changes with Apache 2.0.17-dev
+ *) If a higher-level filter handles the the byterange aspects of a
+ request, then the byterange filter should not try to redo the
+ work. The most common case of this happening, is a byterange
+ request going through the proxy, and the origin server handles
+ the byterange request. The proxy should ignore it.
+ [Graham Leggett <minfrin@sharp.fm>]
+
*) Changed the threaded mpm to have child_main join to each of the
worker threads to make sure the kids are all gone before child_main
exits after a signal (cleanup from perform_idle_server_maintenance).