Yichun Zhang

@wonderbeyond You can always use access_by_lua\* or rewrite_by_lua\* to evaluate the value of your custom nginx variable for `srcache_skip`. Don't use `map`; its lazy evaluation can also lead to surprises.

@wonderbeyond Given that `$srcache_exptime` is not mandatory. The user may or may not use it for its srcache subrequests and ngx_srcache indeed has no control over that and it even...

@wonderbeyond It's possible with `header_filter_by_lua*` if the info is in the upstream response header. But be careful with output filter ordering (better use OpenResty to be sure).

@frozenminds You just need to be careful about running phases of each nginx directives used here. The basic running order in _each_ location is 1. if/rewrite (rewrite phase) 2. srcache_fetch...

@dvershinin Thanks for the report! Mind to contribute a patch? It looks like an easy fix to just adjust the type declaration of `void ...`.

On Thu, Jan 12, 2012 at 3:08 AM, Ricardo Fritsche [email protected] wrote: > Hi! > > FIrst of all, really GREAT work. Im using it with our js/css packer and...

On Sun, Jan 15, 2012 at 12:52 AM, Ricardo Fritsche [email protected] wrote: > @agentzh It looks perfect cause only a small amount of clients would need descompression as IE6 is...

On Mon, Jan 16, 2012 at 6:48 PM, Ricardo Fritsche [email protected] wrote: > I understand. If there is this limitation, no problem to redefine it again in srcache. > >...

@divya84 It's not easy to summarize in a single sentence or two because it's complicated (yes, streaming processing has extra complication, especially in the context of streaming substitutions). I suggest...

@normanjoyner I'd suggest the following options: 1. Cache both compressed and uncompressed responses, and add (a canonical-ized) value of the Accept-Encoding to your cache key. So that clients which do...