diff options
| author | Luca Toscano <elukey@apache.org> | 2016-12-31 10:08:51 +0100 |
|---|---|---|
| committer | Luca Toscano <elukey@apache.org> | 2016-12-31 10:08:51 +0100 |
| commit | 586bb590f5d9dd0cf00cfff2c0a33204bf9c864a (patch) | |
| tree | 88b22f48f3a864754aea5078ad7d395b09c487ee /docs/manual/mod/core.html.en | |
| parent | Removed mod_proxy_protocol references after r1776624 (diff) | |
| download | apache2-586bb590f5d9dd0cf00cfff2c0a33204bf9c864a.tar.xz apache2-586bb590f5d9dd0cf00cfff2c0a33204bf9c864a.zip | |
Core doc page rebuild
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1776707 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/mod/core.html.en')
| -rw-r--r-- | docs/manual/mod/core.html.en | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 50665f4a7b..56c8d6d3c0 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -2054,7 +2054,7 @@ media type in the HTTP Content-Type header field</td></tr> (<a href="https://tools.ietf.org/html/rfc7230#section-3.1.1">RFC 7230 §3.1.1</a>) and the HTTP Request Header Fields (<a href="https://tools.ietf.org/html/rfc7230#section-3.2">RFC 7230 §3.2</a>), which are now applied by default or using the <code>Strict</code> option. Due to legacy modules, applications or - custom user-agents which must be deperecated the <code>Unsafe</code> + custom user-agents which must be deprecated the <code>Unsafe</code> option has been added to revert to the legacy behaviors. These rules are applied prior to request processing, so must be configured at the global or default (first) matching virtual host section, by IP/port @@ -2068,7 +2068,7 @@ media type in the HTTP Content-Type header field</td></tr> risks of accepting non-conformant request messages, while <a href="https://tools.ietf.org/html/rfc7230#section-3.5">RFC 7230 §3.5</a> "Message Parsing Robustness" identify the risks of accepting obscure whitespace and request message formatting. - As of the introduction of this directive, all grammer rules of the + As of the introduction of this directive, all grammar rules of the specification are enforced in the default <code>Strict</code> operating mode, and the strict whitespace suggested by section 3.5 is enforced and cannot be relaxed.</p> @@ -2099,7 +2099,7 @@ media type in the HTTP Content-Type header field</td></tr> <p><a href="https://tools.ietf.org/html/rfc2616#section-19.6">RFC 2616 §19.6</a> "Compatibility With Previous Versions" had encouraged HTTP servers to support legacy HTTP/0.9 requests. RFC 7230 - superceeds this with "The expectation to support HTTP/0.9 requests has + supersedes this with "The expectation to support HTTP/0.9 requests has been removed" and offers additional comments in <a href="https://tools.ietf.org/html/rfc7230#appendix-A">RFC 7230 Appendix A</a>. The <code>Require1.0</code> option allows the user to remove support of the default <code>Allow0.9</code> option's @@ -3942,7 +3942,7 @@ as if 'QualifyRedirectURL ON' was configured.</td></tr> <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Core</td></tr> <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>core</td></tr> </table> -<p>HTTP Methods that are not conforming to the relvant RFCs are normally +<p>HTTP Methods that are not conforming to the relevant RFCs are normally rejected by request processing in Apache HTTPD. To avoid this, modules can register non-standard HTTP methods they support. The <code class="directive">RegisterHttpMethod</code> allows to register such |