[PATCH]

Hello docs,

Here's a little patch for new_features_2_2.xml.fr (2.2.x and trunk branches)

Lucien

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

mod_rewrite docs

Re: mod_rewrite docs

2008/8/13 Rich Bowen <rbowen <at> rcbowen.com>:
> I think I've decided to focus on the trunk docs, but if someone wanted to
> apply patches to 2.2, I expect that there are folks who would appreciate
> that.

I'll be your backscra^H^H^Hport monkey.

--

-- 
noodl

Re: mod_rewrite docs

Rich Bowen wrote:

> I've finally resurfaced, and am once again tinkering with the 
> mod_rewrite documentation. My goal is to have the rewrite guide be full 
> of actual useful real-world examples, and stuff that folks are actually 
> asking on IRC and the users <at>  list, and to have the explanations be 
> actual explanations, rather than just "don't think, just do this" recipes.
> 
> I'd also like to get all of the stuff in the ill-fated 
> rewrite.drbacchus.com into either the real docs, or into the official 
> wiki, so that I can retire that hardware before it gives up the ghost.
> 
> So I expect for a while it will look like I'm just flailing about 
> aimlessly, but I have a general plan in mind, and I hope I'm moving in 
> that direction. Although one can hope that HTTPD 3.0 will make 
> mod_rewrite nothing more than an unpleasant memory, for the moment it's 
> one of our biggest support burdens, at least on IRC, and I naively 
> believe that this could be helped by better documentation, and better 
> examples.
> 
> I think I've decided to focus on the trunk docs, but if someone wanted 
> to apply patches to 2.2, I expect that there are folks who would 
> appreciate that. I don't know how cleanly the patches will apply back to 
> 2.0, but perhaps that's worth doing, too.
> 
I know that there is a patch due to come to dev <at>  shortly for mod_rewrite 
which adds an extra flag ;-

--

-- 

-----------------------------------------
Tony Stevenson
tony <at> pc-tony.com  //  pctony <at> apache.org
http://www.pc-tony.com/

1024D/51047D66 ECAF DC55 C608 5E82 0B5E  3359 C9C7 924E 5104 7D66
-----------------------------------------

Re: svn commit: r685418 - in /httpd/httpd/trunk/docs/manual/rewrite: rewrite_guide.html.en rewrite_guide.xml

On Tue, Aug 12, 2008 at 10:12 PM,  <rbowen <at> apache.org> wrote:

> +RewriteCond %{HTTP_REFERER} !www.example.com [NC]

Not likely a factor in this example, but maybe better in the guide
(where people will derive from) to use != or escape/anchor the
expression?

If we leave it as a regex, maybe include somethimg like  ^(www\.)?... too

--

-- 
Eric Covener
covener <at> gmail.com

Re: svn commit: r685418 - in /httpd/httpd/trunk/docs/manual/rewrite: rewrite_guide.html.en rewrite_guide.xml

Re: svn commit: r685838 - in /tomcat/site/trunk: docs/security.html xdocs/security.xml

I love the way you phrased this, httpd should steal this for our site :)

Bill

markt <at> apache.org wrote:
> Author: markt
> Date: Thu Aug 14 03:07:25 2008
> New Revision: 685838
> 
> URL: http://svn.apache.org/viewvc?rev=685838&view=rev
> Log:
> Make purpose of security mailing list even clearer. Could now just provide a link to this page in response
to non-issue mails to the security address.
> 
> Modified:
>     tomcat/site/trunk/docs/security.html
>     tomcat/site/trunk/xdocs/security.xml
> 
> Modified: tomcat/site/trunk/docs/security.html
> URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/security.html?rev=685838&r1=685837&r2=685838&view=diff
> ==============================================================================
> --- tomcat/site/trunk/docs/security.html (original)
> +++ tomcat/site/trunk/docs/security.html Thu Aug 14 03:07:25 2008
>  <at>  <at>  -262,17 +262,36  <at>  <at> 
>      <p>The Apache Software Foundation takes a very active stance in eliminating
>         security problems and denial of service attacks against Apache Tomcat.
>         </p>
> +
>      <p>We strongly encourage folks to report such problems to our private
>         security mailing list first, before disclosing them in a public forum.</p>
>  
>      <p>
> -<strong>We cannot accept regular bug reports or other queries at this
> -       address, we ask that you use our <a href="bugreport.html">bug reporting
> -       page</a> for those. All mail sent to this address that does not relate to
> -       security problems in the Apache Tomcat source code will be ignored.
> -       </strong>
> +<strong>Please note that the security mailing list should only be used
> +       for reporting undisclosed security vulnerabilities in Apache Tomcat and
> +       managing the process of fixing such vulnerabilities. We cannot accept
> +       regular bug reports or other queries at this address. All mail sent to
> +       this address that does not relate to an undisclosed security problem in
> +       the Apache Tomcat source code will be ignored.</strong>
>  </p>
> -    <p>The mailing address is: <a href="mailto:security <at> tomcat.apache.org">
> +
> +    <p>If you need to report a bug that isn't an undisclosed security
> +       vulnerability, please use the <a href="bugreport.html">bug reporting
> +       page</a>.</p>
> +       
> +    <p>Questions about:</p>
> +    <ul>
> +      <li>how to configure Tomcat securely</li>
> +      <li>if a vulnerability applies to your particular application</li>
> +      <li>obtaining further information on a published vulnerability</li>
> +      <li>availability of patches and/or new releases</li>
> +    </ul>
> +    <p>should be address to the users mailing list. Please see the
> +       <a href="lists.html">mailing lists</a> page for details of how to
> +       subscribe.</p>
> +    
> +    <p>The private security mailing address is:
> +       <a href="mailto:security <at> tomcat.apache.org">
>         security <at> tomcat.apache.org</a>
>  </p>
>  
> 
> Modified: tomcat/site/trunk/xdocs/security.xml
> URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/security.xml?rev=685838&r1=685837&r2=685838&view=diff
> ==============================================================================
> --- tomcat/site/trunk/xdocs/security.xml (original)
> +++ tomcat/site/trunk/xdocs/security.xml Thu Aug 14 03:07:25 2008
>  <at>  <at>  -48,15 +48,34  <at>  <at> 
>      <p>The Apache Software Foundation takes a very active stance in eliminating
>         security problems and denial of service attacks against Apache Tomcat.
>         </p>
> +
>      <p>We strongly encourage folks to report such problems to our private
>         security mailing list first, before disclosing them in a public forum.</p>
>  
> -    <p><strong>We cannot accept regular bug reports or other queries at this
> -       address, we ask that you use our <a href="bugreport.html">bug reporting
> -       page</a> for those. All mail sent to this address that does not relate to
> -       security problems in the Apache Tomcat source code will be ignored.
> -       </strong></p>
> -    <p>The mailing address is: <a href="mailto:security <at> tomcat.apache.org">
> +    <p><strong>Please note that the security mailing list should only be used
> +       for reporting undisclosed security vulnerabilities in Apache Tomcat and
> +       managing the process of fixing such vulnerabilities. We cannot accept
> +       regular bug reports or other queries at this address. All mail sent to
> +       this address that does not relate to an undisclosed security problem in
> +       the Apache Tomcat source code will be ignored.</strong></p>
> +
> +    <p>If you need to report a bug that isn't an undisclosed security
> +       vulnerability, please use the <a href="bugreport.html">bug reporting
> +       page</a>.</p>
> +       
> +    <p>Questions about:</p>
> +    <ul>
> +      <li>how to configure Tomcat securely</li>
> +      <li>if a vulnerability applies to your particular application</li>
> +      <li>obtaining further information on a published vulnerability</li>
> +      <li>availability of patches and/or new releases</li>
> +    </ul>
> +    <p>should be address to the users mailing list. Please see the
> +       <a href="lists.html">mailing lists</a> page for details of how to
> +       subscribe.</p>
> +    
> +    <p>The private security mailing address is:
> +       <a href="mailto:security <at> tomcat.apache.org">
>         security <at> tomcat.apache.org</a></p>
>  
>      <p>Note that all networked servers are subject to denial of service attacks,
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe <at> tomcat.apache.org
> For additional commands, e-mail: dev-help <at> tomcat.apache.org
> 
> 
> 

Re: [PATCH]

Çarşamba 06 Ağustos 2008 19:50 sularında, Lucien GENTIS şunları yazmıştı: 
> Hello docs,
> 
> Here's a little patch for new_features_2_2.xml.fr (2.2.x and trunk branches)
> 
> Lucien
> 

Committed.
http://svn.apache.org/viewvc?rev=683335&view=rev
http://svn.apache.org/viewvc?rev=683338&view=rev

Nilgün

Re: svn commit: r686547 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

On 08/18/2008 02:48 PM, Nilgün Belma Bugüner wrote:
> Cumartesi 16 Ağustos 2008 22:26 sularında, rpluem <at> apache.org şunları yazmıştı: 
>> Author: rpluem
>> Date: Sat Aug 16 12:26:50 2008
>> New Revision: 686547
>>
>> URL: http://svn.apache.org/viewvc?rev=686547&view=rev
>> Log:
>> * Fix error in default setting for ProxyTimeout
>>
>> Modified:
>>     httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
>>
> validate-xml:
> [xmlvalidate] /arsiv/apache/docs/trunk/manual/mod/mod_proxy.xml:1316:73: The content of
element type "default" must match "(br)".
> [xmlvalidate] /arsiv/apache/docs/trunk/manual/mod/mod_proxy.xml is not a valid XML document

Thanks for pointing out. I adjusted the dtd in r686853 accordingly.

Regards

Rüdiger

SSLCertificateChainFile grammar issue

The second paragraph of this directive's explanation ends "That's
usually not one expect."

Should that be "That's not usually what one expects."? The next
paragraph takes some parsing too.

I've no idea what this directive does so thought I'd best ask for
clarification 

--

-- 
noodl