a) did not set it
-Original Message-
From: squid-announce [mailto:squid-announce-boun...@lists.squid-cache.org] On
Behalf Of Amos Jeffries
Sent: Thursday, 18 January 2018 16:17
To: squid-annou...@lists.squid-cache.org
Subject: [squid-announce] RFC: Squid ESI processor changes
The Squid
On 23/01/18 03:10, Adam Majer wrote:
> On 01/18/2018 04:16 PM, Amos Jeffries wrote:
>> The Squid team are planning to remove the Custom XML parser used for ESI
>> processing from the next Squid version.
>
> For next squid version, do you mean 5.x? next 4.x release? or s
On 01/18/2018 04:16 PM, Amos Jeffries wrote:
> The Squid team are planning to remove the Custom XML parser used for ESI
> processing from the next Squid version.
For next squid version, do you mean 5.x? next 4.x release? or stable
3.5.x release?
proposed new default? libxml2?
)
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
with these "minimal build" the compilation is successfull :
--build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include
--mandir=${prefix}/share/man --infodir=${prefix}/share/info
--sysconfdir=/etc
--localstatedir=/var --libexecdir=${prefix}/lib/squid3 --srcdir=.
Hi Massimo,
what arguments are you using for ./configure?
$ ./configure --help|fgrep -i esi
--enable-esiEnable ESI for accelerators. Benefits from expat or
libxml2. Enabling ESI will cause squid reverse
proxies to be capable
can I disable ESI ?
[ environment : debian 8.2, linux 3.16 64 bit ]
best regards, Massimo
OPT="--build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include
--mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc"
OPT="$OPT --localstatedir=/var --libe
configuration variables
3- fully integrate libTrie into squid's build system. Unless Robert
knows otherwise, squid is the only user of this library..
I cannot tell what libTrie does: The README file is empty and the commit
message only implies that it is an ESI component. AFAICT, only ESI uses
it today
libTrie does: The README file is empty and the commit
message only implies that it is an ESI component. AFAICT, only ESI uses
it today.
From what I understand (Robert, can you come to the rescue?) libTrie
is a very optimized key- and prefix- lookup engine, trading memory
useage for speed. It would
of this library..
I cannot tell what libTrie does: The README file is empty and the commit
message only implies that it is an ESI component. AFAICT, only ESI uses
it today.
From what I understand (Robert, can you come to the rescue?) libTrie
is a very optimized key- and prefix- lookup engine, trading
for speed. It would be great to use in the Http parser to look
up header keys, for instance.
It is a generic trie implementation, it is very good at some forms of
lookup, and it's used in ESI yes; I had planned to try it in the HTTP
parser, but ETIME.
I do not know much about ESI, but IMHO, if somebody
. It would be great to use in the Http parser to look
up header keys, for instance.
It is a generic trie implementation, it is very good at some forms of
lookup, and it's used in ESI yes; I had planned to try it in the HTTP
parser, but ETIME.
I do not know much about ESI, but IMHO, if somebody has
of this library..
I cannot tell what libTrie does: The README file is empty and the commit
message only implies that it is an ESI component. AFAICT, only ESI uses
it today.
From what I understand (Robert, can you come to the rescue?) libTrie
is a very optimized key- and prefix- lookup engine
libTrie into squid's build system. Unless Robert
knows otherwise, squid is the only user of this library..
I cannot tell what libTrie does: The README file is empty and the commit
message only implies that it is an ESI component. AFAICT, only ESI uses
it today.
From what I understand (Robert
that it is an ESI component. AFAICT, only ESI uses
it today.
I do not know much about ESI, but IMHO, if somebody has cycles to work
on this, it would be best to spend them removing ESI (together with
libtTrie) from Squid sources while converting ESI into an eCAP adapter.
This will be a big step forward towards
New patch attached resolving most of the issues identified below.
On 21/03/2013 6:12 p.m., Alex Rousskov wrote:
On 03/20/2013 09:34 PM, Amos Jeffries wrote:
The attached patch adds the Key: header on Squid generated ESI responses
so that any receiving clients which support the new header
On 03/21/2013 08:20 AM, Amos Jeffries wrote:
On 21/03/2013 6:12 p.m., Alex Rousskov wrote:
On 03/20/2013 09:34 PM, Amos Jeffries wrote:
The attached patch adds the Key: header on Squid generated ESI responses
so that any receiving clients which support the new header are able to
use
The Key: header being proposed for standardization replaces and extends
the Vary header to provide more fine-grained variant selection by caches.
The attached patch adds the Key: header on Squid generated ESI responses
so that any receiving clients which support the new header are able to
use
On 03/20/2013 09:34 PM, Amos Jeffries wrote:
The attached patch adds the Key: header on Squid generated ESI responses
so that any receiving clients which support the new header are able to
use it for handling our pages.
I do not understand how a receiving client can actually use the Key
Hi all,
What is in your opinion the right behavior wrt ESI in configure,
default-maybe (enabled if all dependencies are present) or
default-disable? The latter is what is curerntly in, but I'm concerned
it may be due to a bug in configure.ac.
Thanks
--
/kinkie
On 27/12/2012 2:07 a.m., Kinkie wrote:
Hi all,
What is in your opinion the right behavior wrt ESI in configure,
default-maybe (enabled if all dependencies are present) or
default-disable? The latter is what is curerntly in, but I'm concerned
it may be due to a bug in configure.ac.
Thanks
tor 2012-12-27 klockan 13:38 +1300 skrev Amos Jeffries:
IIRC it is still off because it is not wanted by many installations and
adds a large footprint to the binary. The more useful
surrogate-capabilities sub-component is auto-enabled on reverse-proxy
traffic regardless of ESI.
Plus still
On Sep 29, 2011, at 9:42 AM, Robert Collins wrote:
On Thu, Sep 29, 2011 at 10:37 AM, Jan Algermissen
jan.algermis...@nordsc.com wrote:
Hi,
I am thinking about trying out some ideas building upon ESI 1.0 and would
like to extend the ESI implementation of Squid. For personal use right now
).
Ah, I did not yet know Squid had an async programming model. Even better. The
current ESI Implementation is non-blocking, too?
Yup, for sure.
-Rob
On Thu, Sep 29, 2011 at 10:37 AM, Jan Algermissen
jan.algermis...@nordsc.com wrote:
Hi,
I am thinking about trying out some ideas building upon ESI 1.0 and would
like to extend the ESI implementation of Squid. For personal use right now,
but if turns out to be valuable I am happy to share
Hi,
I am thinking about trying out some ideas building upon ESI 1.0 and would like
to extend the ESI implementation of Squid. For personal use right now, but if
turns out to be valuable I am happy to share it.
I downloaded the source yesterday and took a short look at the ESI parts
Amos, in response to your IRC question:
with these ESI changes are you confident enough that we can now
auto-enable ESI for 3.1.0.14?
Answer:
Not until the autoconf foo stuff for the parsers have settled in trunc.
A default build of 3.1 should not strictly require libxml2 and expat and
should
Amos Jeffries has voted approve.
Status is now: Approved
Comment:
Not having tested. But changes are minimal.
For details, see:
http://bundlebuggy.aaronbentley.com/project/squid/request/%3C49C00843.7040005%40measurement-factory.com%3E
Project: Squid
SourceLayout: esi/, take 1
Moved src/ESI* files into src/esi/.
Renamed ESI source files from ESIFoo.{cc,cci,h} to Foo.{cc,cci,h}.
Replaced implicit constructor-based Parser registration with an explicit
call
to Esi::Init() which knows of all ESI parsers. Added Esi::Clean counterpart.
Made
Bundle Buggy has detected this merge request.
For details, see:
http://bundlebuggy.aaronbentley.com/project/squid/request/%3C49C00843.7040005%40measurement-factory.com%3E
Project: Squid
the wiki page if
my changes (based on that consensus) are approved.
src/adaptation/
src/adaptation/icap
src/adaptation/ecap
Do ESI files belong to adaptation/esi even though they do not use common
adaptation interfaces or even the same vectoring points? It feels like
we should leave ESI
changes (based on that consensus) are approved.
src/adaptation/
src/adaptation/icap
src/adaptation/ecap
Do ESI files belong to adaptation/esi even though they do not use common
adaptation interfaces or even the same vectoring points? It feels like
we should leave ESI out of adaptation
Thomas-Martin Seck wrote:
Hi,
I noticed that squid-3 does not seem to like --enable-esi in conjunction
with --disable-optimizations. A build where both options are defined
fails as follows; builds where either option is defined work.
(This is 3.0.STABLE12 on FreeBSD 7, first observed on amd64
Hi,
I noticed that squid-3 does not seem to like --enable-esi in conjunction
with --disable-optimizations. A build where both options are defined
fails as follows; builds where either option is defined work.
(This is 3.0.STABLE12 on FreeBSD 7, first observed on amd64 by the
FreeBSD ports
Hi ,
I have following query.
In the following function in ESICustomParser.cc I have passed the
reference of ESIVarstate . This works fine.
bool
ESICustomParser::parse(char const *dataToParse, size_t const
lengthOfData, bool const endOfStream,ESIVarState *var) .
But when I try to pass the
Thanks Amos.
On Thu, Aug 28, 2008 at 5:14 PM, Amos Jeffries [EMAIL PROTECTED] wrote:
Paras Fadte wrote:
Hi,
Can anybody please tell me from the below link what type is
parserState ? It is just below the ParserState class .( it
has a comment - /* todo factor this off somewhere else;
Paras Fadte wrote:
Hi,
Can anybody please tell me from the below link what type is
parserState ? It is just below the ParserState class .( it
has a comment - /* todo factor this off somewhere else; */ )
http://squid.treenet.co.nz/Doc/Code/ESIContext_8h-source.dyn
Sorry for the
On Thu, 2008-04-17 at 11:00 +0530, Paras Fadte wrote:
ESI seems to be very buggy which comes by default with squid for
example see my following post which I had sent over a month ago to
which nobody responded.
Is there a bug report for that specific question? I recall seeing
somebody (Henrik
be simple.
-Paras
On Thu, Apr 17, 2008 at 12:07 PM, Alex Rousskov
[EMAIL PROTECTED] wrote:
On Thu, 2008-04-17 at 11:00 +0530, Paras Fadte wrote:
ESI seems to be very buggy which comes by default with squid for
example see my following post which I had sent over a month ago to
which nobody
On Thu, 2008-04-17 at 09:38 +0530, Paras Fadte wrote:
Also can I get any help regarding development of ESI in squid?
I have not seen much ESI activity for a long while so I would not expect
much help. What exactly are you interested in when it comes to ESI
development?
Thanks,
Alex.
On Sat, 10 Nov 2007, Randall DuCharme wrote:
Ok this is strange. It looks like it's trying to compile ESI
specific support in yet I've not done --enable-esi. In autoconf.h
#define ESI 0 is present. I've removed the -Werror flag for now
so the multiple inclusion warning shouldn't
and likely to be
chosen by some other project or operating system that uses an ESI
acronym.
Seems slightly messier, but I see your point, and it will do.
Amos
and likely to be
chosen by some other project or operating system that uses an ESI
acronym.
hi,
it's me again :)
i'm wondering if (parts of) the ESI invalidation protocol (http://
www.esi.org/invalidation_protocol_1-0.html) are implemented in squid3?
browsing cvs / greping the code didn't reveal a lot information.
thanks
jodok
--
Lovely Systems, Partner
phone: +43 5572 908060
hi,
as mentioned earlier i'm working on squid3/esi support for zope3.
yay! i got my first template assembled a few hours ago, but soon i
ran across http://www.squid-cache.org/bugs/show_bug.cgi?id=1566
(i've been running squid-3.0.PRE5)
now i'm trying to get CVS head running, but i fail
hi there,
i'm jodok from lovely systems - an austrian company developing zope3
applications.
we need some ESI support to scale portals of our customers and would
like to give squid3 a try.
during this week we're sitting on a hut in the austrian alps (http://
www.lovelysystems.com/snowsprint
anything about it at the moment, but I suspect it would be reasonably
easy to add a selector at configure time to choose the library with a
default to libxml2, since it seems the best supported at this time (but
I could be wrong--again, I'm not terribly familiar with ESI or the Squid
Hi,
Robert Collins wrote:
Cool. I don't recall the libxml2 push api being present when I wrote the
esi code.
I think it was introduced somewhere in the 2.5.x or 2.6.x releases, but I
don't know exactly...
please file a bug in bugzilla with the patch as per our developer
guidelines.
It's filed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my name is Joachim Bauch and I'd like to contribute to Squid3, especially in
the area of ESI and -depending on spare time- help with some porting to Windows.
I already startet to implement a patch against the current CVS HEAD of Squid3
that uses
On Fri, 26 Mar 2004, Pascal Peregrina wrote:
Hi,
I would like to know what you think about adding a enable/disable ESI
directive either in squid.conf or a command line switch...
Maybe.. depends on how much of the data flow ESI needs to touch..
Regards
Henrik
Every ESI include seems to increment client.http_requests. Is there any
reliable way to get how many actual client requests squid has processed
not including ESI sub-requests?
We are trying squid 3 as a reverse proxy with ESI.
This is the error in the log when I try to visitate an ESI page on my
CachePeer:
ESI subrequest failed transfer
This message is reported 3 times, because our esi page import 3 php pages.
We have a cache peer on the same host of squid
On Wed, 2003-08-27 at 14:30, Henrik Nordstrom wrote:
On Wednesday 27 August 2003 16.12, Brian Akins wrote:
esi:include src=www.cnn.com/index.html onerror=continue /
Is it intentional that the URL is relative? I suspect you want
http://www.cnn.com/index.html there...
Regards
Henrik
-- Forwarded Message --
Subject: Question about Squid ESI implementation
Date: Sat, 8 Mar 2003 13:11:16 -0700
From: Vincent, Merlin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Hello -
I'm a graduate student at the University of Colorado, and I am
working on a thesis that explores
Well, a week late, but it's done. I've merged the ESI code into HEAD.
I haven't (as yet) followed Henriks lead and moved the surrogate-id
logic into a per-peer struct, but I don't regress any of the accelerator
logic either.
Enjoy.
Cheers,
Rob
--
GPG key available at: http
55 matches
Mail list logo
