httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Rumph <mike.ru...@oracle.com>
Subject Re: svn commit: r1675471 - in /httpd/httpd/trunk/docs/manual/mod: core.xml mod_mime.xml
Date Wed, 22 Apr 2015 19:45:20 GMT
Hello Eric,

This changed gives the following error when ./build.sh validate-xml is run:

Buildfile: build.xml

validate-xml:
[xmlvalidate] /home/mrumph/httpd-trunk/docs/manual/mod/core.xml:1916:7: 
The element type "p" must be terminated by the matching end-tag "</p>".

BUILD FAILED
/home/mrumph/httpd-trunk/docs/manual/style/lang-targets.xml:294: Could 
not validate document /home/mrumph/httpd-trunk/docs/manual/mod/core.xml

Thanks,

Mike

On 4/22/2015 12:37 PM, covener@apache.org wrote:
> Author: covener
> Date: Wed Apr 22 19:37:03 2015
> New Revision: 1675471
>
> URL: http://svn.apache.org/r1675471
> Log:
>
> reword per feedback
>
> Modified:
>      httpd/httpd/trunk/docs/manual/mod/core.xml
>      httpd/httpd/trunk/docs/manual/mod/mod_mime.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=1675471&r1=1675470&r2=1675471&view=diff
> ==============================================================================
> --- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
> +++ httpd/httpd/trunk/docs/manual/mod/core.xml Wed Apr 22 19:37:03 2015
> @@ -1892,18 +1892,27 @@ ForceType image/gif
>       static files, where the generator of the response typically specifies
>       a Content-Type, this directive has no effect.</p>
>   
> +
>       <note><title>Note</title>
> +    <p>If no handler is explicitly set for a request, the specified content
> +    type will also be used as the handler name. </p>
> +
>       <p>When explicit directives such as
>       <directive module="core" >SetHandler</directive> or
>       <directive module="mod_mime">AddHandler</directive> do not apply
>       to the current request, the internal handler name normally set by those
> -    directives is set to match the content type specified by this directive.
> +    directives is instead set to the content type specified by this directive.
> +    <p>
>       This is a historical behavior that some third-party modules
> -    (such as mod_php) may use "magic" content types used only to signal the
> -    module to take responsibility for the matching request.  Configurations
> -    that rely on such "magic" types should be avoided by the use of
> +    (such as mod_php) may look for a "synthetic" content type used only to
> +    signal the module to take responsibility for the matching request.
> +    </p>
> +
> +    <p>Configurations that rely on such "synthetic" types should be avoided.
> +    Additionally, configurations that restrict access to
>       <directive module="core" >SetHandler</directive> or
> -    <directive module="mod_mime">AddHandler</directive>. </p>
> +    <directive module="mod_mime">AddHandler</directive> should
> +    restrict access to this directive as well.</p>
>       </note>
>   
>   </usage>
>
> Modified: httpd/httpd/trunk/docs/manual/mod/mod_mime.xml
> URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_mime.xml?rev=1675471&r1=1675470&r2=1675471&view=diff
> ==============================================================================
> --- httpd/httpd/trunk/docs/manual/mod/mod_mime.xml (original)
> +++ httpd/httpd/trunk/docs/manual/mod/mod_mime.xml Wed Apr 22 19:37:03 2015
> @@ -610,17 +610,25 @@ AddType application/rss+xml;qs=0.8 .xml
>   
>   
>       <note><title>Note</title>
> +    <p>If no handler is explicitly set for a request, the specified content
> +    type will also be used as the handler name. </p>
> +
>       <p>When explicit directives such as
>       <directive module="core" >SetHandler</directive> or
>       <directive module="mod_mime">AddHandler</directive> do not apply
>       to the current request, the internal handler name normally set by those
> -    directives is set to match the content type specified by this directive.
> +    directives is instead set to the content type specified by this directive.
> +    <p>
>       This is a historical behavior that some third-party modules
> -    (such as mod_php) may use "magic" content types used only to signal the
> -    module to take responsibility for the matching request.  Configurations
> -    that rely on such "magic" types should be avoided by the use of
> +    (such as mod_php) may look for a "synthetic" content type used only to
> +    signal the module to take responsibility for the matching request.
> +    </p>
> +
> +    <p>Configurations that rely on such "synthetic" types should be avoided.
> +    Additionally, configurations that restrict access to
>       <directive module="core" >SetHandler</directive> or
> -    <directive module="mod_mime">AddHandler</directive>. </p>
> +    <directive module="mod_mime">AddHandler</directive> should
> +    restrict access to this directive as well.</p>
>       </note>
>   
>   </usage>
>
>
>
>


Mime
View raw message