# -> this is what Plone sees as the "real" HTTP request URL. # Note that domain name spelling in VirtualHostBase URL matters Server_name access_log /var/log/nginx/ Įrror_log /var/log/nginx/ # (you could also do the opposite www -> non-www domain) # This specifies which IP and port Plone is running on. #add_header Content-Security-Policy "default-src 'self' img-src * style-src 'unsafe-inline' script-src 'unsafe-inline' 'unsafe-eval'" Īdd_header Content-Security-Policy-Report-Only "default-src 'self' img-src * style-src 'unsafe-inline' script-src 'unsafe-inline' 'unsafe-eval'" Like that, but Plone processes are externallyĪdd_header Strict-Transport-Security "max-age=15768000 includeSubDomains" Īdd_header X-XSS-Protection "1 mode=block" Īdd_header X-Content-Type-Options "nosniff" Nginx does not spawn Plone process or anything Serves the requests from port 8080 - Nginx acts simpleĪs a HTTP proxy between Medusa and outgoing port 80 Plone itself contains a mini web server (Medusa) which Written - Plone uses the URL to link stylesheets also. It is a sign that VirtualHostMonster URL is incorrectly If your site loads without CSS styles usually Uses to construct links in the template ( portal_url The URL passed to VirtualHostMonster is the URL Plone Plone/Zope in any way, because all the installers willĪutomatically install one for you. You don't need to configure VirtualHostMonster in Sites are nested in the Zope application server as paths Want to site be served from port 80 root (/), but Plone We also need to rewrite the request path, because you VirtualHostMonster provides a way to rewrite the request To pass the original protocol and hostname to Plone. Plone will by default be served on port 8080.These instructionsĪre not for configurations where one uses theīuildout configuration tool to build a static Nginx This is a minimal configuration to run nginx on Minimal Nginx front end configuration for Plone on
0 kommentar(er)
