get_send_file_max_age() on the application or blueprint. Default: timedelta(hours=12) (43200 seconds) SERVER_NAME Inform the application what host and port it is bound to. Required for subdomain route matching PROPAGATE_EXCEPTIONS, PRESERVE_CONTEXT_ON_EXCEPTION New in version 0.6: MAX_CONTENT_LENGTH New in version 0.5: SERVER_NAME New in version 0.4: LOGGER_NAME 1.11.4 Configuring from Files Configuration becomes more useful application served on localhost at port 8000, setting appro- priate headers: server { listen 80; server_name _; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; location / { proxy_pass

get_send_file_max_age() on the application or blueprint. Default: timedelta(hours=12) (43200 seconds) SERVER_NAME Inform the application what host and port it is bound to. Required for subdomain route matching application served on localhost at port 8000, setting appropriate headers: server { listen 80; server_name _; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; location host_matching attribute. Defaults to False. subdomain_matching – consider the subdomain relative to SERVER_NAME when matching routes. Defaults to False. template_folder – the folder that contains the templates

attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. New in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment

attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. New in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment

attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. Added in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment

information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. New in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject

information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. New in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject

information specified in the trusted proxy headers. This will setup the following variables: HTTP_HOST SERVER_NAME SERVER_PORT REMOTE_ADDR REMOTE_PORT (if available) wsgi.url_scheme Waitress also has support for surrounding the IP address with brackets. Added in version 1.0. server_name This is the value that will be placed in the WSGI environment as SERVER_NAME, the only time that this value is used in the WSGI environment attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name. Please see the documentation for server_name in https://docs.pylonsproject

URLs, etc. It is configured with the ServerName directive, and it is available to CGIs via the SERVER_NAME environment variable. The actual value used at run time is controlled by the UseCanonicalName setting /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1 ## and now deal with CGIs - we have to force a MIME type RewriteCond %{REQUEST_URI} ^/cgi-bin/ RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 ^/cgi-bin/ # check the hostname is right so that the RewriteRule works RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$ # concatenate the virtual host name onto the start of the URI # the

URLs, etc. It is configured with the ServerName directive, and it is available to CGIs via the SERVER_NAME environment variable. The actual value used at run time is controlled by the UseCanonicalName setting /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1 ## and now deal with CGIs - we have to force a MIME type RewriteCond %{REQUEST_URI} ^/cgi-bin/ RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 ^/cgi-bin/ # check the hostname is right so that the RewriteRule works RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$ # concatenate the virtual host name onto the start of the URI # the