[EMAIL PROTECTED] wrote:
Log:
Remove proxyhost and proxyport from pre_request hook.
They are not needed for finding apropriate worker.
They are needed for the use of mod_proxy as a forward proxy.
The correct way of handling these in the AJP case is to DECLINE the
request if proxyhost and
[EMAIL PROTECTED] wrote:
Log:
Remove proxyhost and proxyport from pre_request hook.
They are not needed for finding apropriate worker.
Reading this again, I see better what is happening.
The proxyhost and proxyport are used when a downstream proxy is used,
would the balancer ever want to
Graham Leggett wrote:
Log:
Remove proxyhost and proxyport from pre_request hook.
They are not needed for finding apropriate worker.
They are needed for the use of mod_proxy as a forward proxy.
The correct way of handling these in the AJP case is to
DECLINE the request if
Mladen Turk wrote:
The removed proxyhost and port are from new hook 'pre_request' that is used
to obtain a valid worker and/or balancer for a scheme.
It has nothing to do with the way the connection is going to be made.
Cool, this makes sense.
The load balancer if present will decide to which
Seams that the minotaur is behaving badly, so I'm getting mails with couple
of hours delay :)
Graham Leggett wrote:
The way that the worker connects to backend depends on
scheme handler
itself (direct or via proxy).
The worker connection itself will be either bound to the client
