ted.
Yes this is true. The question is: Is this wrong?
If this is considered wrong, we need to split ap_proxy_get_worker
into two functions or we need to add a boolean parameter longest_match to it.
In the case of the request processing we need longest match whereas in the
configuration case me m
Plüm wrote:
-Ursprüngliche Nachricht-
Von: Jean-frederic Clere
Gesendet: Mittwoch, 12. Juli 2006 14:21
An: dev@httpd.apache.org
Betreff: ap_proxy_get_worker
Hi,
Why does ap_proxy_get_worker() gives the best matched worker? -
Shouldn't it give the exact match -
Nor
Jean-frederic Clere wrote:
>
> Why does ap_proxy_get_worker() gives the best matched worker? -
> Shouldn't it give the exact match -
>
No, because most of the times the URL isn't an "exact"
mat
> -Ursprüngliche Nachricht-
> Von: Jean-frederic Clere
> Gesendet: Mittwoch, 12. Juli 2006 14:21
> An: dev@httpd.apache.org
> Betreff: ap_proxy_get_worker
>
>
> Hi,
>
> Why does ap_proxy_get_worker() gives the best matched worker? -
> Shouldn'
Hi,
Why does ap_proxy_get_worker() gives the best matched worker? -
Shouldn't it give the exact match -
Cheers
Jean-Frederic
