You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stefan Fritsch <sf...@sfritsch.de> on 2011/10/03 21:12:24 UTC
Axe ap_proxy_removestr() ?
Hi,
ap_proxy_removestr() uses memory that grows quadratically with the number
of fields in the input string, which is bad. It was introduced in r88648
(Apr 2001) but hasn't been used after r91370 (Oct 2001). Any objection
if I just remove it?
Cheers,
Stefan
Re: Axe ap_proxy_removestr() ?
Posted by Jim Jagielski <ji...@jaguNET.com>.
Axe on trunk.
On Oct 3, 2011, at 3:12 PM, Stefan Fritsch wrote:
> Hi,
>
> ap_proxy_removestr() uses memory that grows quadratically with the number of fields in the input string, which is bad. It was introduced in r88648 (Apr 2001) but hasn't been used after r91370 (Oct 2001). Any objection if I just remove it?
>
> Cheers,
> Stefan
>
Re: Axe ap_proxy_removestr() ?
Posted by Rüdiger Plüm <ru...@vodafone.com>.
Am 03.10.2011 21:12, schrieb Stefan Fritsch:
> Hi,
>
> ap_proxy_removestr() uses memory that grows quadratically with the
> number of fields in the input string, which is bad. It was introduced
> in r88648 (Apr 2001) but hasn't been used after r91370 (Oct 2001). Any
> objection if I just remove it?
>
> Cheers,
> Stefan
+1 on trunk.
Regards
Rüdiger
Re: Axe ap_proxy_removestr() ?
Posted by Graham Leggett <mi...@sharp.fm>.
On 03 Oct 2011, at 9:12 PM, Stefan Fritsch wrote:
> ap_proxy_removestr() uses memory that grows quadratically with the
> number of fields in the input string, which is bad. It was
> introduced in r88648 (Apr 2001) but hasn't been used after r91370
> (Oct 2001). Any objection if I just remove it?
Go ahead, +1.
Regards,
Graham
--