nginx
Docker image: Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found
As soon as you’ve setup the certificate in nginx, I see no sense enabling it in the asp.net core container as your docker network is going to be visible to public via nginx. To disable Kestrel Https listening just remove 443 port from the following code: – ASPNETCORE_URLS=https://+:443;http://+:80 Replace it with: – ASPNETCORE_URLS=http://+:80 With .NET … Read more
What is the benefit of using NginX for Node.js?
Here http://developer.yahoo.com/yui/theater/video.php?v=dahl-node Node.js author says that Node.js is still in development and so there may be security issues that NginX simply hides. On the other hand, in case of a heavy traffic NginX will be able to split the job between many Node.js running servers.
Configuring Nginx for large URIs
I have found the solution. The problem was that there were multiple instances of nginx running. This was causing a conflict and that’s why the large_client_header_buffers wasnt working. After killing all nginx instances I restarted nginx with the configuration: client_header_buffer_size 64k; large_client_header_buffers 4 64k; Everything started working after that. Hope this helps anyone facing this … Read more
how to issue a relative url redirect from nginx?
There is an nginx directive absolute_redirect available from nginx version 1.11.8, which is enabled by default. If disabled, redirects issued by nginx will be relative. This issue is a bit older, but maybe useful for all of you hitting it from google. absolute_redirect off;
Does the nginx “upstream” directive have a port setting?
in your upstream configuration you have ports defined ( 6666 and 9999 ), those are the ports your backend servers need to listen on the proxy_pass directive doesn’t need an additional port configuration in this case. Your nginx listens on port 81 which you’ve defined in the listen directive Is this what you tried to … Read more
X-Forwarded-Proto and Flask
You are missing the ProxyFix() middleware component. See the Flask Proxy Setups documentation. There is no need to subclass anything; simply add this middleware component to your WSGI stack: # Werkzeug 0.15 and newer from werkzeug.middleware.proxy_fix import ProxyFix from flask import Flask app = Flask(__name__) app.wsgi_app = ProxyFix(app.wsgi_app, x_proto=1) If you have Flask installed, you … Read more
How to use vue.js with Nginx?
Add the following code to your Nginx Config, as detailed in the VueRouter docs, here: location / { try_files $uri $uri/ /index.html; } Also, you need to enable history mode on VueRouter: const router = new VueRouter({ mode: ‘history’, routes: […] })
Get NGINX to serve .gz compressed asset files
1) ensure you have Nginx > 1.2.x (to proper headers modifications) and compile with –with-http_gzip_static_module option 2) Enable this option gzip on (to serve back-end response with gzip header) 3) Setup assets location with gzip_static on (to serve all.css.gz, all.js.gz files directly) 4) Prevent of etag generation and last-modify calculation for assets 5) Turn on … Read more