Bug 62167 - 2.4 docs should warn about ProxyPassMatch vs. Workers
Summary: 2.4 docs should warn about ProxyPassMatch vs. Workers
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.4.29
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-08 22:11 UTC by Eric Covener
Modified: 2018-04-02 16:39 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Covener 2018-03-08 22:11:44 UTC
See #43513 -- this code is not in 2.4 and "most" ProxyPassMatch will define
a worker that won't be matched later.  The docs should warn in at least the Worker section.
Comment 1 Yann Ylavic 2018-03-08 22:57:55 UTC
Should we revive the patch currently in STALLED section?
Comment 2 Luca Toscano 2018-04-02 07:18:45 UTC
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..)
Comment 3 Eric Covener 2018-04-02 16:39:26 UTC
(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.