svn commit: r1855987 - /httpd/httpd/branches/2.4.x/STATUS

[ji...@apache.org]

Author: jim
Date: Thu Mar 21 13:26:54 2019
New Revision: 1855987

URL: http://svn.apache.org/viewvc?rev=1855987&view=rev
Log:
Backport vote 100

Modified:
    httpd/httpd/branches/2.4.x/STATUS

Modified: httpd/httpd/branches/2.4.x/STATUS
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?rev=1855987&r1=1855986&r2=1855987&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/STATUS (original)
+++ httpd/httpd/branches/2.4.x/STATUS Thu Mar 21 13:26:54 2019
@@ -203,7 +203,7 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
                   http://svn.apache.org/r1853953
                   http://svn.apache.org/r1853956
      2.4.x patch: http://people.apache.org/~ylavic/patches/httpd-2.4.x-forward_100_continue-v4.patch
-     +1: ylavic, icing
+     +1: ylavic, icing, jim
      ylavic: please note the "s/ASCII_(CRLF|ZERO)/\1_ASCII/g" in the backport,
              same as in trunk (where definitions come from httpd.h) so doing
              the change now in 2.4.x helps backports. Since in 2.4.x these

Opt-in/out for proxy 100-Continue?

[Yann Ylavic <yl...@gmail.com>]

>       2.4.x patch: http://people.apache.org/~ylavic/patches/httpd-2.4.x-forward_100_continue-v4.patch
> +     +1: ylavic, icing, jim

After this patch mod_proxy will forward (and follow) 100-continue in
any case, possibly something depended on 100 continue being responded
(handled) by httpd itself, so I wonder if we'd better not have a new
Proxy100Continue on/off for this.

Don't we want a way to keep previous behaviour somehow here? in/out?


PS: sorry for thinking about it only now..