You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2017/12/19 19:06:22 UTC
svn commit: r1818701 - /httpd/httpd/trunk/docs/manual/mod/core.xml
Author: covener
Date: Tue Dec 19 19:06:21 2017
New Revision: 1818701
URL: http://svn.apache.org/viewvc?rev=1818701&view=rev
Log:
clarify/reword RegisterHTTPMethod and add some seealso's
Modified:
httpd/httpd/trunk/docs/manual/mod/core.xml
Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1818701&r1=1818700&r2=1818701&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Tue Dec 19 19:06:21 2017
@@ -5097,13 +5097,14 @@ hostname or IP address</description>
<contextlist><context>server config</context></contextlist>
<usage>
-<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 <directive>RegisterHttpMethod</directive> allows to register such
-methods manually. This can be useful if such methods are forwarded
-for external processing, e.g. to a CGI script.</p>
+<p>This directive may be used to register additional HTTP methods. This is
+necessary if non-standard methods need to be used with directives that accept
+method names as parameters, or to allow particular non-standard methods to be
+used via proxy or CGI script when the server has been configured to only pass
+recognized methods to modules.</p>
</usage>
+<seealso><directive module="core">HTTPProtocolOptions</directive></seealso>
+<seealso><directive module="mod_allowmethods">AllowMethods</directive></seealso>
</directivesynopsis>
<directivesynopsis>