Re: Cache based on custom header

Yes you can. For some subtle custom cache logic I needed to use openresty, which is an nginx bundle that adds a lot of customization points. Sent from my iPhone > On Feb 8, 2017, at 5:47 PM, Chad Hansen via nginx wrote: > > I use nginx as a reverse proxy, and upstream clients

Cache based on custom header

I use nginx as a reverse proxy, and upstream clients have a need for my service to cache differently than downstream servers. Is there a way to change what header nginx uses to accept cache settings? Or a way to re-write cache headers before the cache settings take affect? For example, I could

[nginx] Request body: c->error on "100 Continue" errors (ticket #1194).

details: http://hg.nginx.org/nginx/rev/92e771de7d89 branches: changeset: 6903:92e771de7d89 user: Maxim Dounin date: Wed Feb 08 19:35:31 2017 +0300 description: Request body: c->error on "100 Continue" errors (ticket #1194). diffstat:

[nginx] Request body: commented out debug printing of old buffers.

details: http://hg.nginx.org/nginx/rev/5e2423bce883 branches: changeset: 6904:5e2423bce883 user: Maxim Dounin date: Wed Feb 08 19:36:03 2017 +0300 description: Request body: commented out debug printing of old buffers. This is not really needed in practice, and

What does the "event timer add" step in the debug log signify?

i am having a problem with trying to use oauth services in that the callback from the provider gets “stuck” on my server. The logs in the pastebin here: http://pastebin.com/qncJKVwQ summarise the experience. Nginx is setup as reverse proxy to Apache which handles PHP using CGI. that is, the old

Re: Nginx only sends hostname to syslog.

Hello! On Wed, Feb 08, 2017 at 09:05:19AM +0100, B.R. via nginx wrote: > From what I read > , > 'host name' aka name of the host is a FQDN in the hostname.domain format ( > domain being able to have n level-s). Just

Re: Nginx only sends hostname to syslog.

Correct me if I am wrong, since I probably will. >From what I read , 'host name' aka name of the host is a FQDN in the hostname.domain format ( domain being able to have n level-s). Thus, it seems that setting a FQDN as