Fix misc typos in comments (#228)
This commit is contained in:
parent
e64b4a6ee2
commit
e30032165c
|
@ -4,7 +4,7 @@
|
|||
#
|
||||
# Drop requests for unknown hosts
|
||||
#
|
||||
# If no default server is defined, nginx will use the first found server.
|
||||
# If no default server is defined, Nginx will use the first found server.
|
||||
# To prevent host header attacks, or other potential problems when an unknown
|
||||
# servername is used in a request, it's recommended to drop the request
|
||||
# returning 444 "no response".
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
#
|
||||
# Drop requests for unknown hosts
|
||||
#
|
||||
# If no default server is defined, nginx will use the first found server.
|
||||
# If no default server is defined, Nginx will use the first found server.
|
||||
# To prevent host header attacks, or other potential problems when an unknown
|
||||
# servername is used in a request, it's recommended to drop the request
|
||||
# returning 444 "no response".
|
||||
|
|
|
@ -2,8 +2,8 @@
|
|||
# | Config file for example.com host |
|
||||
# ----------------------------------------------------------------------
|
||||
#
|
||||
# This file is a template for a nginx server.
|
||||
# This nginx server listen the `example.com` host and handle requests.
|
||||
# This file is a template for an Nginx server.
|
||||
# This Nginx server listens for the `example.com` host and handles requests.
|
||||
# Replace `example.com` with your hostname before enabling.
|
||||
|
||||
# Choose between www and non-www, listen on the wrong one and redirect to
|
||||
|
|
|
@ -2,8 +2,8 @@
|
|||
# | Config file for non-secure example.com host |
|
||||
# ----------------------------------------------------------------------
|
||||
#
|
||||
# This file is a template for a non-secure nginx server.
|
||||
# This nginx server listen the `example.com` host and handle requests.
|
||||
# This file is a template for a non-secure Nginx server.
|
||||
# This Nginx server listens for the `example.com` host and handles requests.
|
||||
# Replace `example.com` with your hostname before enabling.
|
||||
|
||||
# Choose between www and non-www, listen on the wrong one and redirect to
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
# the visible content from within the `/.well-known/` hidden directory.
|
||||
#
|
||||
# These types of files usually contain user preferences or the preserved
|
||||
# state of an utility, and can include rather private places like, for
|
||||
# state of a utility, and can include rather private places like, for
|
||||
# example, the `.git` or `.svn` directories.
|
||||
#
|
||||
# The `/.well-known/` directory represents the standard (RFC 5785) path
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
# users visit your website using a Google Image Search results page).
|
||||
#
|
||||
# Nonetheless, you should ensure that you send the `X-Frame-Options`
|
||||
# header for all pages that allow a user to make a state changing
|
||||
# header for all pages that allow a user to make a state-changing
|
||||
# operation (e.g: pages that contain one-click purchase links, checkout
|
||||
# or bank-transfer confirmation pages, pages that make permanent
|
||||
# configuration changes, etc.).
|
||||
|
|
|
@ -13,7 +13,7 @@
|
|||
# https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_certificate
|
||||
#
|
||||
# (2) Intermediate certificate location if loaded certificate (1) does not
|
||||
# contain intermediate certificate when enabling OCSP stanpling.
|
||||
# contain intermediate certificate when enabling OCSP stapling.
|
||||
#
|
||||
# https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_trusted_certificate
|
||||
#
|
||||
|
|
|
@ -4,8 +4,8 @@
|
|||
|
||||
# OCSP is a lightweight, only one record to help clients verify the
|
||||
# validity of the server certificate.
|
||||
# OCSP stapling allow the server to send its cached OCSP record during
|
||||
# the TLS handshake, whithout the need of 3rd party OCSP responder.
|
||||
# OCSP stapling allows the server to send its cached OCSP record during
|
||||
# the TLS handshake, without the need of 3rd party OCSP responder.
|
||||
#
|
||||
# https://wiki.mozilla.org/Security/Server_Side_TLS#OCSP_Stapling
|
||||
# https://tools.ietf.org/html/rfc6066#section-8
|
||||
|
|
|
@ -2,16 +2,16 @@
|
|||
# | Cache file-descriptors |
|
||||
# ----------------------------------------------------------------------
|
||||
|
||||
# This tells nginx to cache open file handles, "not found" errors and
|
||||
# This tells Nginx to cache open file handles, "not found" errors and
|
||||
# metadata about files and their permissions.
|
||||
#
|
||||
# Based on these cached metadata, nginx can immediately begin sending
|
||||
# Based on these cached metadata, Nginx can immediately begin sending
|
||||
# data when a popular file is requested, and will also know to
|
||||
# immediately send a 404 if a file is missing on disk, and so on.
|
||||
#
|
||||
# (!) It also means that the server won't react immediately to changes
|
||||
# on disk, which may be undesirable.
|
||||
# As only metadata are cached, edited files may be troncated until
|
||||
# As only metadata are cached, edited files may be truncated until
|
||||
# the cache is refreshed.
|
||||
# https://github.com/h5bp/server-configs-nginx/issues/203
|
||||
#
|
||||
|
|
Loading…
Reference in New Issue