https://issues.apache.org/bugzilla/show_bug.cgi?id=46709
Christoph Anton Mitterer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #4 from Christoph Anton Mitterer <[email protected]> --- I see the same (version 2.2.22)... having a HTTP 1.0 only backend with force-proxy-request-1.0 set. The client sends an "Expect: 100-continue" Apache (correctly follows the RFC) and returns 417. I don't say that this is a bug in Apache, since AFAIU it does what the RFC says but rather from the clients... And even if one would unset force-proxy-request-1.0 it wouldn't really make things better, since while it would work then, the RFC would be more or less broken ... or at least the functionality of "Expect: 100-continue" wouldn't work. The only solution right now seems to strip the header, which is IMHO not very nice though, as Expect may get further use (even if right now only 100-continue is defined). Therefore, can re-opening this with the question whether you can reconsider the patch from comment #2. It would allow to only ignore 100-continue, and not any other future values for Expect: . -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
