| Summary: | 2.4 docs should warn about ProxyPassMatch vs. Workers | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Eric Covener <covener> |
| Component: | Documentation | Assignee: | HTTP Server Documentation List <docs> |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.4.29 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Eric Covener
2018-03-08 22:11:44 UTC
Should we revive the patch currently in STALLED section? Eric one clarification: "won't be matched later" means that a ProxyPassMatch worker will not be re-used but re-created over and over for each proxied connection? (so no connection re-use if set, etc..) (In reply to Luca Toscano from comment #2) > Eric one clarification: "won't be matched later" means that a ProxyPassMatch > worker will not be re-used but re-created over and over for each proxied > connection? (so no connection re-use if set, etc..) The worker is like a named connection pool. There is a special one called the default reverse proxy worker, but sinc. it doesn't know if/when it will ever be re-used it doesn't cache DNS or keep connections in the pool. So when a request comes in that is proxied due to proxypassmatch, it will consult DNS and get a new TCP Connection then destroy it at the end, unless you go out of your way to define a worker as we tell people to do for the [P] flag in mod_rewrite. |