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

-service server_name:service_mgr. Named pipes When using named pipes, the parameter requires two leading back slashes and the separator is another back slash, as in -service \\server_name\service_mgr

host = env['HTTP_HOST'] except KeyError: host = env['SERVER_NAME'] port = env['SERVER_PORT'] if protocol == 'https': According to PEP-3333, this header # will always be present. host = self.env['SERVER_NAME'] return host @property def subdomain(self): # PERF(kgriffs): .partition 'REMOTE_PORT': '65133', 'RAW_URI': '/', 'REMOTE_ADDR': '127.0.0.1', 'SERVER_NAME': host, 'SERVER_PORT': port, 'wsgi.url_scheme': scheme, 'wsgi.input': body