Re: auth_basic and satisfy allowing all traffic

Hi Francis - That would have been my suspicion as well. To test that theory, I installed the same nginx 1.10.1 RPM file on a similar CentOS 6 virtual machine in my environment. This particular VM has never been used for any nginx testing, nor has it ever had nginx installed. I tested the same s

Re: auth_basic and satisfy allowing all traffic

Hi Francis - In both cases, I get a 404 response, which is to be expected as the default doc root for nginx isn't served on my host. I should expect a 401 on the second curl test, but I get a 404. HTTP/1.1 404 Not Found Server: nginx Date: Fri, 14 Apr 2017 03:44:19 GMT Content-Type: text/html Co

auth_basic and satisfy allowing all traffic

Hi all - I'm having an issue trying to get auth_basic and satisfy directives working in tandem. If I use auth_basic/auth_basic_user_file on its own, I am prompted for credentials as expected. However, if I added the satisfy/allow/deny directives above, it seems that ALL traffic is allowed in wit

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

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;

Problem with uwsgi_no_cache

Hi all - I'm attempting to exclude application/json data from storing in nginx's cache. All other content types are OK to cache. I thought that the below config would work for me, but nginx is still caching everything that is proxying. What am I doing wrong? ## in http block ## map $http_c

proxy_pass to upstreams and then 404 location

Hello all - I'm attempting to do the following in nginx and having difficulty with the last step in this succession. 1) In / location, proxy_pass to Django upstream. 2) proxy_intercept_errors is on in this block and does a proxy_pass to PHP upstream if 404 is returned. 3) In PHP location block (i

nginx and WordPress in a subdirectory

Hello - I've got nginx as a front-end to Apache and am trying to serve a single WordPress site from a location on my site. Right now I would like to test the location, but it will eventually be served as /advertise. I cannot get the WordPress site to serve correctly, however as I am seeing a 301