From: Eric Covener Date: Mon, 2 Apr 2012 13:26:11 +0000 (+0000) Subject: xforms X-Git-Tag: 2.4.2~36 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3da010eea7561d43fe6186e0db17ab93e00b7935;p=apache xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1308346 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en index a98e69a023..598bbf0f74 100644 --- a/docs/manual/mod/mod_rewrite.html.en +++ b/docs/manual/mod/mod_rewrite.html.en @@ -112,40 +112,40 @@ URLs on the fly Status:Extension Module:mod_rewrite -

The RewriteBase directive explicitly - sets the base URL-path (not filesystem directory path!) for per-directory rewrites - that result in the substitution of a relative path. - When you use a RewriteRule - in a .htaccess file, mod_rewrite strips off - the local directory prefix before processing, then rewrites the rest of - the URL. When the rewrite is completed, mod_rewrite - automatically adds the local directory prefix (or the - RewriteBase when set) back on to the substitution - before handing it back to the core of the server as if it were the original - URL.

- -

This directive is required for per-directory rewrites whose context - is a directory made available via the Alias - directive, when the substitution uses a relative path.

- -

If your URL path does not exist verbatim on the filesystem, - or isn't directly under your DocumentRoot, - you must use RewriteBase in every - .htaccess file where you want to use RewriteRule directives.

- -

The example below demonstrates how to map - http://example.com/myapp/index.html to - /home/www/example/newsite.html, in a .htaccess file. This - assumes that the content available at - http://example.com/ is on disk at /home/www/example/

+

The RewriteBase directive specifies the + URL prefix to be used for per-directory (htaccess) + RewriteRule directives that substitute a relative + path.

+

This directive is required when you use a relative path + in a substitution in per-directory (htaccess) context unless either + of the following conditions are true: +

+

+ +

In the example below, RewriteBase is necessary + to avoid rewriting to http://example.com/opt/myapp-1.2.3/welcome.html + since the resource was not relative to the document root. This + misconfiguration would normally cause the server to look for an "opt" + directory under the document root.

+DocumentRoot /var/www/example.com
+Alias /myapp /opt/myapp-1.2.3
+<Directory /opt/myapp-1.2.3>
 RewriteEngine On
-# The URL-path used to get to this context, not the filesystem path
 RewriteBase /myapp/
-RewriteRule ^index\.html$  newsite.html
+RewriteRule ^index\.html$  welcome.html 
+</Directory>
-
top

RewriteCond Directive

diff --git a/docs/manual/programs/ab.html.en b/docs/manual/programs/ab.html.en index a0bd125bbe..33e2479f50 100644 --- a/docs/manual/programs/ab.html.en +++ b/docs/manual/programs/ab.html.en @@ -31,8 +31,8 @@

See also

top
@@ -207,57 +207,7 @@
top
-

Bugs

-

There are various statically declared buffers of fixed length. Combined - with the lazy parsing of the command line arguments, the response headers - from the server and other external inputs, this might bite you.

- -

It does not implement HTTP/1.x fully; only accepts some 'expected' forms - of responses. The rather heavy use of strstr(3) shows up top - in profile, which might indicate a performance problem; i.e., you - would measure the ab performance rather than the server's.

-
top
-
-

Example Output

- -

Sample output is provided here.

- 
Server Software:        Apache/2.2.17
-Server Hostname:        testserver.com
-Server Port:            80
-
-Document Path:          /index.html
-Document Length:        787 bytes
-
-Concurrency Level:      5
-Time taken for tests:   0.436 seconds
-Complete requests:      1000
-Failed requests:        0
-Write errors:           0
-Total transferred:      1026000 bytes
-HTML transferred:       787000 bytes
-Requests per second:    2292.26 [#/sec] (mean)
-Time per request:       2.181 [ms] (mean)
-Time per request:       0.436 [ms] (mean, across all concurrent requests)
-Transfer rate:          2296.74 [Kbytes/sec] received
-
-Connection Times (ms)
-              min  mean[+/-sd] median   max
-Connect:        0    1   0.4      1       3
-Processing:     1    1   0.4      1       3
-Waiting:        0    1   0.5      1       2
-Total:          2    2   0.1      2       3
-
-Percentage of the requests served within a certain time (ms)
-  50%      2
-  66%      2
-  75%      2
-  80%      2
-  90%      2
-  95%      2
-  98%      2
-  99%      3
- 100%      3 (longest request)
- +

Description of output

The output may vary depending on the command line parameters given. Possible output with a brief explanation of each element is listed below.

@@ -342,6 +292,17 @@ Percentage of the requests served within a certain time (ms)
The rate of transfer as calculated by the formula totalread / 1024 / timetaken
+
top
+
+

Bugs

+

There are various statically declared buffers of fixed length. Combined + with the lazy parsing of the command line arguments, the response headers + from the server and other external inputs, this might bite you.

+ +

It does not implement HTTP/1.x fully; only accepts some 'expected' forms + of responses. The rather heavy use of strstr(3) shows up top + in profile, which might indicate a performance problem; i.e., you + would measure the ab performance rather than the server's.

Available Languages:  en  |