Add support for 'nocache' flag to map directive
Sorin Manole
sorin.v.manole at gmail.com
Tue Nov 29 05:18:39 UTC 2016
Would it make sense to add nocacheable if input_var or one of the variables
in the value options is nocacheable?
On Mon, 28 Nov 2016 at 12:58, Eran Kornblau <eran.kornblau at kaltura.com>
wrote:
> Hi all,
>
>
>
> I created this post yesterday - https://forum.nginx.org/read.php?10,271197
>
> And thought about submitting a patch for it.
>
> Before I do, I wanted to check with you whether this is something you’ll
> be willing to accept
> (assuming the implementation is correct, according to standards, doesn’t
> break things etc.)
>
>
>
> In short, the idea is to add an optional flag to the map directive that
> make the map module
> pass NGX_HTTP_VAR_NOCACHEABLE in its call to ngx_http_add_variable.
>
> The conf structure will look like:
>
> map $input_var $output_var nocache {
>
> default 0;
>
> "some value" 1;
>
> }
>
>
>
> Thank you,
>
>
>
> Eran
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20161129/501e79c2/attachment.html>
More information about the nginx-devel
mailing list