nginx “fails fast” when the client informs it that it’s going to send a body larger than the client_max_body_size by sending a 413 response and closing the connection. Most clients don’t read responses until the entire request body is sent. Because nginx closes the connection, the client sends data to the closed socket, causing a … Read more
location ~ /issue([0-9]+) { return 301 http://example.com/shop/issues/custom_isse_name$1; }
I had the same problem. It was because I had accidentally used a relative path with the symbolic link. Are you sure you used full paths, e.g.: ln -s /etc/nginx/sites-available/example.com.conf /etc/nginx/sites-enabled/example.com.conf
In HTTP world, the “upstream server” term was introduced in the HTTP/1.0 specification, RFC 1945: 502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. Formal definition was added later, in RFC 2616: upstream/downstream Upstream and downstream … Read more
Okay, I think I get this now. Why can’t nginx directly call my Flask application? Because nginx doesn’t support the WSGI spec. Technically nginx could implement the WSGI spec if they wanted, they just haven’t. That being the case, we need a web server that does implement the spec, which is what the uWSGI server … Read more
I know it is kind an old post, but I’ve had the same problem and couldn’t understand why your code didn’t work. After a LOT of tests I’ve found out why. It seems like fpm receives the full path from nginx and tries to find the files in the fpm container, so it must be … Read more
As of nginx 1.8.0, the correct solution is sudo nginx -t && sudo service nginx reload Note that due to a bug, configtest always returns a zero exit code even if the config file has an error.
It’s a server, yes. A node.js web application is a full-fledged web server just like Nginx or Apache. You can indeed serve your node.js application without using any other web server. Just change your code to: app = express(); http.createServer(app).listen(80); // serve HTTP directly Indeed, some projects use node.js as the front-end load balancer for … Read more
Edit your listen statement from: listen 443; to listen 443 ssl; and comment out or delete : # ssl on; then check nginx -t again.