Mailing List Archive

#352: ESI can't process gzipped documents
----------------------+-----------------------------------------------------
Reporter: toledo | Owner: phk
Type: defect | Status: closed
Priority: normal | Milestone: Varnish 2.0 code complete
Component: varnishd | Version: trunk
Severity: normal | Resolution: invalid
Keywords: esi gzip |
----------------------+-----------------------------------------------------
Changes (by phk):

* status: new => closed
* resolution: => invalid

Comment:

I will move this one to the "post 2.0" wikipage, it is not a bug under the
current specification for varnish.

If at some point we implement support for this, I don't see it as a "101"
level feature.

Getting all the bits and pieces of an ESI page compressed so that they can
be concatenated as a compressed object is not a trivial undertaking, and
not getting it right means that you spend a lot of cpu time compressing
objects that only one client will see.

In particular I have a hard time seeing the benefit from compressing the
page on the backend, uncompressing it on varnish, doing ESI, and then
compressing the result for the client.

--
Ticket URL: <http://varnish.projects.linpro.no/ticket/352#comment:1>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

#352: ESI can't process gzipped documents
----------------------+----------------------------------------
Reporter: toledo | Owner: phk
Type: defect | Status: closed
Priority: normal | Milestone: Varnish 2.0 code complete
Component: varnishd | Version: trunk
Severity: normal | Resolution: invalid
Keywords: esi gzip |
----------------------+----------------------------------------

Comment (by keretamalam):

I am about to leave and cannot look into this further right now, but I do
want to mention that relying on pkg-config itself is not a problem (as you
said, we also use it later), the problem is that on some systems, the .pc
file for pkg-config is supplying wrong information (whereas on yours, it's
botan-config that is wrong), so that's why I'm trying to make it work with
both (while one of them is bad).
[http://maskodoq.blogspot.com/2014/03/unit-link-terbaik-di-indonesia.html
Unit Link Terbaik di Indonesia Commonwealth Life Investra Link]
[http://maskodoq.blogspot.com/2013/07/CiptoJunaedy.html Cipto Junaedy]
[http://etnisjawa.blogspot.com/2013/08/apakah-cipto-junaedy-bohong.html
Cipto Junaedy]

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/352#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

#352: ESI can't process gzipped documents
----------------------+----------------------------------------
Reporter: toledo | Owner: phk
Type: defect | Status: closed
Priority: normal | Milestone: Varnish 2.0 code complete
Component: varnishd | Version: trunk
Severity: normal | Resolution: invalid
Keywords: esi gzip |
----------------------+----------------------------------------

Comment (by adminah):

I am about to leave and cannot look into this further right now, but I do
want to mention that relying on pkg-config itself is not a problem (as
you
said, we also use it later), the problem is that on some systems, the .pc
file for pkg-config is supplying wrong information (whereas on yours,
it's
botan-config that is wrong), so that's why I'm trying to make it work
with
both (while one of them is bad).

[http://komputermesh.blogspot.com/2015/03/martabak.html Martabak Paling
Enak di Jakarta]
[http://komputermesh.blogspot.com/2015/04/berbagi-bahagia-bersama-
tabloidnovacom.html Berbagi Bahagia Bersama Tabloidnova.com]
[http://komputermesh.blogspot.com/2015/05/synthesis.html Synthesis
Development – Indonesia Developer Property]</a>

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/352#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs