Edit: it seems nginx now supports error_log stderr; as mentioned in Anon’s answer. You can send the logs to /dev/stdout. In nginx.conf: daemon off; error_log /dev/stdout info; http { access_log /dev/stdout; … } edit: May need to run ln -sf /proc/self/fd /dev/ if using running certain docker containers, then use /dev/fd/1 or /dev/fd/2
It looks like one possible answer is, unsurprisingly, curl: $ curl http://example.com/ –silent –write-out “%{size_download}\n” –output /dev/null 31032 $ curl http://example.com/ –silent -H “Accept-Encoding: gzip,deflate” –write-out “%{size_download}\n” –output /dev/null 2553 In the second case the client tells the server that it supports content encoding and you can see that the response was indeed shorter, compressed.
It’s used for proxying requests to other servers. An example from http://wiki.nginx.org/LoadBalanceExample is: http { upstream myproject { server 127.0.0.1:8000 weight=3; server 127.0.0.1:8001; server 127.0.0.1:8002; server 127.0.0.1:8003; } server { listen 80; server_name www.domain.com; location / { proxy_pass http://myproject; } } } This means all requests for / go to the any of the servers … Read more
One permission requirement that is often overlooked is a user needs x permissions in every parent directory of a file to access that file. Check the permissions on /, /home, /home/demo, etc. for www-data x access. My guess is that /home is probably 770 and www-data can’t chdir through it to get to any subdir. … Read more
Well, I think nginx by itself doesn’t have that in its setup, because the Ubuntu-maintained package does it as a convention to imitate Debian’s apache setup. You could create it yourself if you wanted to emulate the same setup. Create /etc/nginx/sites-available and /etc/nginx/sites-enabled and then edit the http block inside /etc/nginx/nginx.conf and add this line … Read more
Following nginx documentation, you can set client_max_body_size 20m ( or any value you need ) in the following context: context: http, server, location
Try location ~ ^/(first/location|second/location)/ { … } The ~ means to use a regular expression for the url. The ^ means to check from the first character. This will look for a / followed by either of the locations and then another /.
You need to use the alias directive for location /static: server { index index.html; server_name test.example.com; root /web/test.example.com/www; location /static/ { alias /web/test.example.com/static/; } } The nginx wiki explains the difference between root and alias better than I can: Note that it may look similar to the root directive at first sight, but the document … Read more
It looks like you are using a custom Kubernetes Cluster (using minikube, kubeadm or the like). In this case, there is no LoadBalancer integrated (unlike AWS or Google Cloud). With this default setup, you can only use NodePort or an Ingress Controller. With the Ingress Controller you can setup a domain name which maps to … Read more
From the HTTP core module docs: Directives with the “=” prefix that match the query exactly. If found, searching stops. All remaining directives with conventional strings. If this match used the “^~” prefix, searching stops. Regular expressions, in the order they are defined in the configuration file. If #3 yielded a match, that result is … Read more