headers
Markus Elfring | 1 Aug 2003 17:51
Picon

Improve documentation for directive "RewriteRule"

Hallo,

I suggest to enhance the documentation for the directive "RewriteRule".

1. http://www.apacheref.com/ref/mod_rewrite/RewriteRule.html
Each parameter should be described in a separate section to improve the readability.

1.1 url-new
Please add a link for the complete explanation to the url-pattern.
- How big can the numbers for back-references be?
- List of server variables

1.2 flags
The flag arguments are described in a single paragraph. I would prefer an ordered list or table.

2. use cases
2.1 redirections to scripts
Please show examples how additional values can be passed to the url-new argument.
A link to a description for the settings (e. g. rights, properties, programming language) to execute
scripts would help.

2.2 content regeneration mechanism
I am very interested in the feature "On-the-fly Content-Regeneration" that is described shortly in the
document "http://httpd.apache.org/docs-2.1/misc/rewriteguide.html.
(The feature "Document With Autorefresh" has got a Perl code example. A similar one might help for the other
use case.)

2.2.1 parameter passing
I'm not sure if one of the following rules would be the solution.
RewriteCond %{REQUEST_FILENAME}   !-s
(Continue reading)

Permalink | Reply | 2 comments |
headers
André Malo | 1 Aug 2003 18:23
Picon

Re: Improve documentation for directive "RewriteRule"

* Markus Elfring wrote:

> I suggest to enhance the documentation for the directive "RewriteRule".
> 
> 1. http://www.apacheref.com/ref/mod_rewrite/RewriteRule.html

The httpd-docs project has no relation to the page you mentioned. The official
documentation can be found at
<http://httpd.apache.org/docs-2.0/mod/mod_rewrite.html> or
<http://httpd.apache.org/docs/mod/mod_rewrite.html>

However, a mod_rewrite-docs-improvement is planned and we'll take care of your
comments.

Thanks.

nd
Permalink | Reply | 1 comment |
headers
Tetsuya Kitahata | 3 Aug 2003 16:32
Picon
Favicon

[Apache Newsletter Draft] News from Apache HTTP Documentation Project in July, 2003

Dear Apache HTTP Documentation Team, 
(http://httpd.apache.org/docs-project/)

Hello,

I am now in the process of preparing the first all-Apache-wide newsletter.
http://www.apache.org/newsletter/
'The Apache Newsletter Issue 1' ... ASF-wide-newsletter of July 2003,
 which will be published in the middle of August 2003.

Please feel free to write statement/comment/article etc. to
the Apache Newsletter (Issue 1) using ApacheWiki
or in this mailing list. Hope to hear from you.
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1

This 'The Apache Newsletter' will be published as a result of the outgrowth
of the previous 'Jakarta Newsletter' and 'Apache Newsletter' can now
cover all the projects under apache.org including infrastructure,
incubator, xml, webservice, PHP, et cetra.

== WHAT WAS JAKARTA NEWSLETTER?? - http://jakarta.apache.org/site/news/

'The Apache Newsletter Issue 1' will be appeared at
http://www.apache.org/newsletter/200307.html
and the editorial deadline will be 00:00 GMT, 9th August.

ApacheWiki (http://nagoya.apache.org/wiki/apachewiki.cgi) had
been already set up.
If you have anything to be added to the ApacheWiki, please go to
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1
(Continue reading)

Permalink | Reply | 0 comments |
headers
Markus Elfring | 3 Aug 2003 22:54
Picon

Re: Improve mod_rewrite documentation

Thanks.

1. The description "http://httpd.apache.org/docs-2.1/mod/mod_rewrite.html" is better formatted
than "apacheref.com".

2. Has anybody requested a syntax that shows the ruleset processing directly?
I see that it would be easier to understand to specify RewriteConds after the pattern of RewriteRules.

3. I assume that the quoting of special characters is done with a backslash character. I do not know a "slosh".

4. I would like to see a section "related or recommended reading" at the bottom.
- URL Rewriting Guide
- more practical solutions, use cases
- books
- partner sites
- mailing list, forum, news

5. I am missing explanations about concurrent and parallel execution of RewriteRules between web server requests.
5.1 How much has a called script got to do with mutual exclusion or synchronization of the processing?
5.2 Is there a program available that provides a safe environment (e. g. waiting queues, mutexes)?
5.3 Can a script achieve to perform a function only once even if several request want it to be done
simultanously because the result will be the same for all requests in a time period?

6. Would you like to show relations to design patterns?
6.1 Reactor
6.2 Dispatcher
6.3 Notifier
6.4 Acceptor-Connector
6.5 Command-Processor
6.6 Service Handler
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vincent Deffontaines | 4 Aug 2003 17:53
Favicon

Out of date section in "manual/stopping"

Translating more and more docs into french, I have found the last
paragraph of the "/manual/stopping.xml" documentation (in the 2.1 branch)
looks very old and out of date. I suggest it be removed if appropriate, or
at least updated.

Here is what it says :

All architectures have a small race condition in each child
involving the second and subsequent requests on a persistent
HTTP connection (KeepAlive). It may exit after reading the
request line but before reading any of the request headers.
There is a fix that was discovered too late to make 1.2. In
theory this isn't an issue because the KeepAlive client has to
expect these events because of network latencies and server
timeouts. In practice it doesn't seem to affect anything either
-- in a test case the server was restarted twenty times per
second and clients successfully browsed the site without
getting broken images or empty documents.

Vincent

--

-- 
Freedom is slavery.
Ignorance is strength.
War is peace.
                -- George Orwell
Permalink | Reply | 1 comment |
headers
Joshua Slive | 4 Aug 2003 18:52
Picon

Re: Out of date section in "manual/stopping"


On Mon, 4 Aug 2003, Vincent Deffontaines wrote:

> Translating more and more docs into french, I have found the last
> paragraph of the "/manual/stopping.xml" documentation (in the 2.1 branch)
> looks very old and out of date. I suggest it be removed if appropriate, or
> at least updated.

Yes, I agree that looks very out-of-date.  The first paragraph of that
section also looks ancient.  The second paragraph is probably obsolete as
well, but I can't guarentee it.  Anyone have more info?

It would be nice to get rid of the whole section, assuming these race
conditions really are gone.

See:
http://httpd.apache.org/docs-2.0/stopping.html#race

Joshua.
Permalink | Reply | 0 comments |
headers
Joshua Slive | 5 Aug 2003 20:01
Picon

Race conditions in restarts

Does anyone know if there are any race conditions left in the graceful
restart code?  If so, what are the details.

Does this section of documentation have any relevance in 2.0:
http://httpd.apache.org/docs-2.0/stopping.html#race

Joshua.
Permalink | Reply | 1 comment |
headers
Jeff Trawick | 5 Aug 2003 20:33

Re: Race conditions in restarts

Joshua Slive wrote:

> Does anyone know if there are any race conditions left in the graceful
> restart code?  If so, what are the details.

CGI requests initiated during a graceful restart don't work as hoped for 
because the cgid daemon gets bounced before any pending cgi requests are 
handled.
Permalink | Reply | 0 comments |
headers
Milan Roubal | 5 Aug 2003 23:26
Picon

Constant bug

Hi,
in file http://httpd.apache.org/docs-2.0/mod/core.html
there is in section LimitRequestBody Directive
line with text: The default value is defined by the compile-time constant
DEFAULT_LIMIT_REQUEST_BODY (0 as distributed).
This is BUG, this constant was removend in year 1998 :)))
http://www.geocrawler.com/archives/3/420/1998/8/50/2314804/
Please correct it, I don't know what is the present situation about similar
constant.
Please CC me in the answer
    Milan Roubal
    roubm9am <at> barbora.ms.mff.cuni.cz
Permalink | Reply | 1 comment |
headers
nd | 6 Aug 2003 15:43
Picon
Favicon

cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html.en

nd          2003/08/06 06:43:25

  Modified:    htdocs/manual/mod core.html.en
  Log:
  The default_limit_request_body constant was removed some time ago ...

  Submitted by: Milan Roubal <roubm9am <at> barbora.ms.mff.cuni.cz>

  Revision  Changes    Path
  1.254     +1 -3      httpd-docs-1.3/htdocs/manual/mod/core.html.en

  Index: core.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html.en,v
  retrieving revision 1.253
  retrieving revision 1.254
  diff -u -r1.253 -r1.254
  --- core.html.en	31 Jul 2003 19:06:06 -0000	1.253
  +++ core.html.en	6 Aug 2003 13:43:25 -0000	1.254
   <at>  <at>  -2071,9 +2071,7  <at>  <at> 

       <p>This directive specifies the number of <em>bytes</em> from 0
       (meaning unlimited) to 2147483647 (2GB) that are allowed in a
  -    request body. The default value is defined by the compile-time
  -    constant <code>DEFAULT_LIMIT_REQUEST_BODY</code> (0 as
  -    distributed).</p>
  +    request body.</p>

       <p>The LimitRequestBody directive allows the user to set a
       limit on the allowed size of an HTTP request message body
(Continue reading)

Permalink | Reply | 0 comments |

Gmane