[squid-dev] [squid-announce] RFC: Squid ESI processor changes

[Martin Bayreuther]

Hello,

I am running two squid instances (Debian stretch - up to date with 
repos). In both instances, the esi_parser config is commented out.
Changing it to whatever value will not impact performance in my 
situation. (10 machines behind a DSL link, squid taking some load off 
the link)

Regards
Maba

Am 18.01.2018 um 16:16 schrieb Amos Jeffries:
> The Squid team are planning to remove the Custom XML parser used for 
> ESI processing from the next Squid version.
>
> At first this seemed like a simple removal if unused functionality. 
> However during review of the changes it turns out this functionality 
> may be used in many situations when it should not have been.
>
>
> Can people using ESI please provide answers for these questions:
>
>
> What is your setting for esi_parser squid.conf directive?
>
>  a) did not set it
>  b) "expat"
>  c) "libxml2"
>  d) "custom"
>
> If you answered (d), why choose that one?
>
>
> If you answer (a) does setting it explicitly to either of the other 
> parsers cause a large impact on your traffic performance?
>
>   Yes/No
>
> If yes, which did you choose?
>
>  ... and how much of an impact was seen?
>
>
>
> If you are not comfortable answering this to the squid-dev mailing 
> list please feel free to send your responses directly to me.
>
> Amos Jeffries
> The Squid Software Foundation
>
> _______________________________________________
> squid-announce mailing list
> squid-announce at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-announce