Replies: 1 comment
|
I don't know of a single page that documents every checkbox down to the exact generated Nginx directives, but the NPM templates make the important ones fairly clear. For example: Websockets SupportThis adds: proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;So enable it when the upstream application uses WebSocket connections. Cache AssetsThis enables NPM's asset-cache configuration for file extensions such as: Those assets go through Nginx's One thing worth knowing is that this cache configuration is quite aggressive: it ignores some upstream cache-related headers, including So I wouldn't blindly enable "Cache Assets" for every application, especially if it serves user-specific/dynamic content using file-looking URLs. Block Common ExploitsThis includes NPM's A useful way to learn exactly what NPM generated for a particular Proxy Host is to inspect the generated Nginx configuration inside the container after toggling an option. That makes it very easy to compare: vs. and see exactly which directives/includes NPM added. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
is there a page that explains every options available when I create a new record? For example Cache assets, Websockets support...
All reactions