s
> > >> static content file - js/css) in this case we should not execute
> unzip
> > and
> > >> zip plugin at all. But if it is just unzip and gzip plugin we cant
> > >> extrapolate this logic and we will execute gzip/gunzip where it is not
> > >
t; >>> And at this point only ATS know about the "body/data" hooks registered
> >> for transaction, so ATS will know whether it is necessary to unzip
> >> response, because there are "body/data" hooks registered. And on the way
> >> out to t
gt;> trickier too.
>>>>
>>>> Cheers,
>>>>
>>>> -- Leif
>>>>
>>>>
>>>>
>>>>> On Mar 24, 2015, at 7:50 AM, Roland Zink > >
>>>> wrote:
>>>>>
>>>>> I think
Cc: dev@trafficserver.apache.org; Roland Zink; Brian Geffon; Cynthia Gu
Subject: Re: Adding Gzip/Gunzip feature in ATS core
Hmmm I'm not anywhere near a computer but continuations should get called in
the order they were added. Is that not the case ? In the case of global plugins
that'
ll zip the body if
> necessary.
> >
> > -Dzmitry
> >
> > ____
> > From: gang li [portl4t...@gmail.com ]
> > Sent: Tuesday, March 24, 2015 6:38 AM
> > To: dev@trafficserver.apache.org
> > Cc: Roland Zink; Brian Gef
f necessary.
>
> -Dzmitry
>
>
> From: gang li [portl4t...@gmail.com]
> Sent: Tuesday, March 24, 2015 6:38 AM
> To: dev@trafficserver.apache.org
> Cc: Roland Zink; Brian Geffon; Cynthia Gu
> Subject: Re: Adding Gzip/Gunzip feature in ATS c
will zip the body if necessary.
-Dzmitry
From: gang li [portl4t...@gmail.com]
Sent: Tuesday, March 24, 2015 6:38 AM
To: dev@trafficserver.apache.org
Cc: Roland Zink; Brian Geffon; Cynthia Gu
Subject: Re: Adding Gzip/Gunzip feature in ATS core
I got this proble
Sent: Tuesday, March 24, 2015 12:43 PM
> > To: dev@trafficserver.apache.org
> > Cc: Brian Geffon; Cynthia Gu
> > Subject: Re: Adding Gzip/Gunzip feature in ATS core
> >
> > I guess I don't understand why the chaining makes a difference. That's
> what I was aski
ds,
Roland
-Original Message-
From: Leif Hedstrom [mailto:zw...@apache.org]
Sent: Tuesday, March 24, 2015 12:43 PM
To: dev@trafficserver.apache.org
Cc: Brian Geffon; Cynthia Gu
Subject: Re: Adding Gzip/Gunzip feature in ATS core
I guess I don't understand why the chaining makes a difference
zw...@apache.org]
> Sent: Tuesday, March 24, 2015 12:43 PM
> To: dev@trafficserver.apache.org
> Cc: Brian Geffon; Cynthia Gu
> Subject: Re: Adding Gzip/Gunzip feature in ATS core
>
> I guess I don't understand why the chaining makes a difference. That's what I
>
I guess I don't understand why the chaining makes a difference. That's what I
was asking in the previous email. If two plugins are chained, one should be
able to detect gzip or not gzip the same way it does as if it was not chained.
What am I missing ? Does each chained plugin not see the update
ESI should handle these situations correctly. e.g. it won't gzip the
response if it is already gzipped.
So it works fine in a standalone way.
The problems begin when we starts to chain a few of these standalone
transformation plugins together. Each of them will try to do the right
thing when they
> On Mar 23, 2015, at 6:08 PM, Dzmitry Markovich
> wrote:
>
> Hello ATS experts,
>
> Today it is very common that http data that goes to the wire is compressed.
> And we think it is a time to standardize this process in ATS core, since it
> is very common operation.
>
> Today multiple plugi
Giving the plugins a defined order seems to be of general use. Given such a
capability you can then configure a ungzip plugin called first and a gzip
plugin called last.
Note however if no plugin in the middle modifies the body then neither ungzip
nor gzip is necessary and the body can stay com
14 matches
Mail list logo
