Re: uwsgi_cache only caching root location

On Sun, Aug 16, 2015 at 01:16:21AM -0400, daveyfx wrote: Hi there, > uwsgi_ignore_headers Set-Cookie; > > This solved my issue. The header is not being sent on the home page, but is > sent with almost all other pages. Yes, that's the reason in this case. """ If the header includes the “Set-Co

Únete a mí en el Grupo de Meetup AWS User Group Peru

Raul Hugo Noriega te invitó a unirte a Meetup "Hola Ya somos una comunidad Oficial, Pronto realizaremos el Primer MeetUp Unete!" -- AWS User Group Peru AWS Perú es una comunidad, integrada por Ingenieros, Técnicos y Geeks con experiencia en Administración y

Re: uwsgi_cache only caching root location

uwsgi_ignore_headers Set-Cookie; This solved my issue. The header is not being sent on the home page, but is sent with almost all other pages. Thanks for the tips. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261033,261037#msg-261037 ___

Re: uwsgi_cache only caching root location

Realized you asked for the results of both requests. Here's the curl -svo /dev/null output from: Home page: > GET / HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: apps01.njprod.amc:9001 > Accept: */* > < HTTP/1.1 200 OK < X

Re: uwsgi_cache only caching root location

Hi Francis - In the uwsgi logs for my Python application, I see in the request logs: [pid: 15085|app: 0|req: 25/81] 38.103.38.200 () {32 vars in 503 bytes} [Sat Aug 15 22:22:08 2015] GET /congress?mref=nav => generated 108292 bytes in 66 msecs (HTTP/1.1 200) 4 headers in 166 bytes (3 switches on

Re: uwsgi_cache only caching root location

On Sat, Aug 15, 2015 at 02:50:13PM -0400, daveyfx wrote: Hi there, > I'm having an issue where nginx is only caching homepage requests. If i > send requests to my server, the HTML at the homepage is saved, but requests > to any URI otherwise do not save in the cache and upstream_cache_status > r

uwsgi_cache only caching root location

Hello all - I'm having an issue where nginx is only caching homepage requests. If i send requests to my server, the HTML at the homepage is saved, but requests to any URI otherwise do not save in the cache and upstream_cache_status returns with a MISS. How can I fix my config so that requests ot

Re: Problem with uwsgi_no_cache

Thank you, Francis. For anyone wondering what my corrected configuration looks like, here it is. All the JSON content returned by the upstream is now ignored and only caching HTML content as desired. ## cache zone config ## uwsgi_cache_path /var/cache/nginx/files keys_zone=www:10m inactive=10m;

Re: Rewrite rules for "random" subfolders

Great! It is working now, thank you very much :) Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261008,261031#msg-261031 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Rewrite rules for "random" subfolders

Try the below one in the server context ..outside all location blocks. You can enable dedug log and do rewrite_log on; to see if its matching etc. Good Luck! rewrite ^/galleries/album-set/album-2/(.*)-single\.php /galleries/album-set/album-2/single.php?id=$1 last;

Re: header handling

I made the below patch and can now use $upstream_http_x_header for logformat to capture the header X.header in the access log. Does anybody see any issues with the patch? --- src/http/ngx_http_variables.c.orig 2015-08-15 02:19:31.635328112 + +++ src/http/ngx_http_variables.c 2015-08-15 02:19: