Loading docs/manual/mod/core.html.en +4 −4 Original line number Diff line number Diff line Loading @@ -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 Loading @@ -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> Loading Loading @@ -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 Loading Loading @@ -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 Loading Loading
docs/manual/mod/core.html.en +4 −4 Original line number Diff line number Diff line Loading @@ -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 Loading @@ -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> Loading Loading @@ -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 Loading Loading @@ -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 Loading
