Date: Tue, 5 Jul 2016 23:20:42 +0200 Subject: Imported Upstream version 2.4.23 --- docs/manual/howto/access.html.en | 2 +- docs/manual/howto/access.html.fr | 2 +- docs/manual/howto/auth.html.en | 14 +- docs/manual/howto/auth.html.fr | 14 +- docs/manual/howto/auth.html.ja.utf8 | 2 +- docs/manual/howto/auth.html.ko.euc-kr | 2 +- docs/manual/howto/auth.html.tr.utf8 | 3 +- docs/manual/howto/cgi.html.en | 2 +- docs/manual/howto/cgi.html.fr | 2 +- docs/manual/howto/cgi.html.ja.utf8 | 2 +- docs/manual/howto/cgi.html.ko.euc-kr | 2 +- docs/manual/howto/htaccess.html.en | 4 +- docs/manual/howto/htaccess.html.fr | 4 +- docs/manual/howto/htaccess.html.ja.utf8 | 2 +- docs/manual/howto/htaccess.html.ko.euc-kr | 2 +- docs/manual/howto/htaccess.html.pt-br | 2 +- docs/manual/howto/http2.html | 5 + docs/manual/howto/http2.html.en | 277 +++++++++++++++++++++++++++ docs/manual/howto/index.html.en | 14 ++ docs/manual/howto/index.html.fr | 15 ++ docs/manual/howto/public_html.html.en | 16 +- docs/manual/howto/public_html.html.fr | 16 +- docs/manual/howto/public_html.html.ja.utf8 | 2 +- docs/manual/howto/public_html.html.ko.euc-kr | 2 +- docs/manual/howto/public_html.html.tr.utf8 | 3 +- docs/manual/howto/reverse_proxy.html.en | 6 +- docs/manual/howto/ssi.html.en | 6 +- docs/manual/howto/ssi.html.fr | 6 +- docs/manual/howto/ssi.html.ja.utf8 | 2 +- docs/manual/howto/ssi.html.ko.euc-kr | 2 +- 30 files changed, 385 insertions(+), 48 deletions(-) create mode 100644 docs/manual/howto/http2.html create mode 100644 docs/manual/howto/http2.html.en (limited to 'docs/manual/howto') diff --git a/docs/manual/howto/access.html.en b/docs/manual/howto/access.html.en index c9cc7582..c4abfab2 100644 --- a/docs/manual/howto/access.html.en +++ b/docs/manual/howto/access.html.en @@ -35,7 +35,7 @@

Access control with mod_rewrite

More information

Comments

Related Modules and Directives

diff --git a/docs/manual/howto/access.html.fr b/docs/manual/howto/access.html.fr index a9eb4ec8..044681f5 100644 --- a/docs/manual/howto/access.html.fr +++ b/docs/manual/howto/access.html.fr @@ -38,7 +38,7 @@ arbitraires

Utilisation de mod_rewrite pour le contrôle d'accès

Informations complémentaires

Commentaires

Voir aussi

Commentaires

Modules et directives concernés

diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en index 2bbb0f8c..2d0ac72a 100644 --- a/docs/manual/howto/auth.html.en +++ b/docs/manual/howto/auth.html.en @@ -50,7 +50,7 @@ person in

Beyond just authorization

Authentication Caching

More information

Comments

Related Modules and Directives

@@ -563,6 +563,18 @@ Require group GroupName Satisfy are no longer needed. However to provide backwards compatibility for older configurations, these directives have been moved to the mod_access_compat module.

+ +

Note

The directives provided by mod_access_compat have + been deprecated by mod_authz_host. + Mixing old directives like Order, Allow or Deny with new ones like + Require is technically possible + but discouraged. The mod_access_compat module was created to support + configurations containing only old directives to facilitate the 2.4 upgrade. + Please check the upgrading guide for more + information. +

diff --git a/docs/manual/howto/auth.html.fr b/docs/manual/howto/auth.html.fr index d0944ca6..23c070ea 100644 --- a/docs/manual/howto/auth.html.fr +++ b/docs/manual/howto/auth.html.fr @@ -52,7 +52,7 @@ d'authentification autorisation

Mise en cache de l'authentification

Pour aller plus loin . . .

Commentaires

Voir aussi

Commentaires

Modules et directives concernés

@@ -602,6 +602,18 @@ autorisation configurations, ces directives ont été déplacées vers le module mod_access_compat.

Note

Les directives fournies par le module + mod_access_compat sont devenues obsolètes depuis + la refonte du module mod_authz_host. Mélanger d'anciennes + directives comme Order, Allow ou Deny avec des nouvelles comme + Require est techniquement + possible mais déconseillé. En effet, mod_access_compat a + été conçu pour supporter des configurations ne contenant que des anciennes + directives afin de faciliter le passage à la version 2.4. Voir le document + upgrading pour plus de détails. +

diff --git a/docs/manual/howto/auth.html.ja.utf8 b/docs/manual/howto/auth.html.ja.utf8 index 4968c4ad..fde0969a 100644 --- a/docs/manual/howto/auth.html.ja.utf8 +++ b/docs/manual/howto/auth.html.ja.utf8 @@ -50,7 +50,7 @@

è¤‡æ•°ã®ãƒ—ãƒãƒã‚¤ãƒ€ã‚’ä½¿ç”¨ã™ã‚‹

å˜ç´”ãªæ‰¿èªã®ãã®å…ˆ

è¿½åŠ æƒ…å ±

ã‚³ãƒ¡ãƒ³ãƒˆ

å‚ç…§

ã‚³ãƒ¡ãƒ³ãƒˆ

é–¢é€£ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–

diff --git a/docs/manual/howto/auth.html.ko.euc-kr b/docs/manual/howto/auth.html.ko.euc-kr index a144fe3d..077046fd 100644 --- a/docs/manual/howto/auth.html.ko.euc-kr +++ b/docs/manual/howto/auth.html.ko.euc-kr @@ -46,7 +46,7 @@

¹ß»ýÇÒ ¼ö ÀÖ´Â ¹®Á¦Á¡

´Ù¸¥ ¹æ¹ýµµ °¡´ÉÇÑ°¡?

´õ ¸¹Àº Á¤º¸

Comments

Âü°í

Comments

°ü·Ã ¸ðµâ°ú Áö½Ã¾î

diff --git a/docs/manual/howto/auth.html.tr.utf8 b/docs/manual/howto/auth.html.tr.utf8 index 4128964b..acb9fc00 100644 --- a/docs/manual/howto/auth.html.tr.utf8 +++ b/docs/manual/howto/auth.html.tr.utf8 @@ -29,6 +29,7 @@ ko | tr

Bu Ã§eviri gÃ¼ncel olmayabilir. Son deÄŸiÅŸiklikler iÃ§in Ä°ngilizce sÃ¼rÃ¼m geÃ§erlidir.

Kimlik DoÄŸrulama istediÄŸiniz kiÅŸileri teyid etme iÅŸlemidir. Yetkilendirme ise kiÅŸilerin nereye gireceklerine ve hangi bilgiye @@ -48,7 +49,7 @@

Yetkilendirmenin biraz Ã¶tesi

Kimlik DoÄŸrulama ArabelleÄŸi

Daha fazla bilgi

Yorum

AyrÄ±ca bakÄ±nÄ±z:

Yorum

Ä°lgili modÃ¼ller ve YÃ¶nergeler

diff --git a/docs/manual/howto/cgi.html.en b/docs/manual/howto/cgi.html.en index eff16b76..0888b605 100644 --- a/docs/manual/howto/cgi.html.en +++ b/docs/manual/howto/cgi.html.en @@ -36,7 +36,7 @@

What's going on behind the scenes?

CGI modules/libraries

For more information

Comments

Introduction

diff --git a/docs/manual/howto/cgi.html.fr b/docs/manual/howto/cgi.html.fr index 4d1a76a1..39ce995b 100644 --- a/docs/manual/howto/cgi.html.fr +++ b/docs/manual/howto/cgi.html.fr @@ -36,7 +36,7 @@

Que se passe-t-il en coulisse

Bibliothèques et modules CGI

Pour plus d'informations

Commentaires

Voir aussi

Commentaires

Introduction

diff --git a/docs/manual/howto/cgi.html.ja.utf8 b/docs/manual/howto/cgi.html.ja.utf8 index 8abc9f0a..c2088ddf 100644 --- a/docs/manual/howto/cgi.html.ja.utf8 +++ b/docs/manual/howto/cgi.html.ja.utf8 @@ -40,7 +40,7 @@

è£ã§ä½•ãŒèµ·ã“ã£ã¦ã„ã‚‹ã®ã‹?

CGI ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«/ãƒ©ã‚¤ãƒ–ãƒ©ãƒª

æ›´ãªã‚‹æƒ…å ±

ã‚³ãƒ¡ãƒ³ãƒˆ

å‚ç…§

ã‚³ãƒ¡ãƒ³ãƒˆ

ã¯ã˜ã‚ã«

diff --git a/docs/manual/howto/cgi.html.ko.euc-kr b/docs/manual/howto/cgi.html.ko.euc-kr index a26c5e9e..c24f5373 100644 --- a/docs/manual/howto/cgi.html.ko.euc-kr +++ b/docs/manual/howto/cgi.html.ko.euc-kr @@ -38,7 +38,7 @@

µÚ¿¡¼´Â ¹«½¼ ÀÏÀÌ ¹ú¾îÁö´Â°¡?

CGI ¸ðµâ/¶óÀÌºê·¯¸®

´õ ¸¹Àº Á¤º¸...

Comments

Âü°í

Comments

¼Ò°³

diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en index 7902bfb0..415d3426 100644 --- a/docs/manual/howto/htaccess.html.en +++ b/docs/manual/howto/htaccess.html.en @@ -42,7 +42,7 @@ changes on a per-directory basis.

Rewrite Rules in .htaccess files

CGI example

Troubleshooting

Comments

.htaccess files

@@ -272,7 +272,7 @@ changes on a per-directory basis.

</Directory> <Location "/"> - Options +IncludesNoExec -ExecCGI
+ Options +IncludesNoExec -ExecCGI </Location> diff --git a/docs/manual/howto/htaccess.html.fr b/docs/manual/howto/htaccess.html.fr index 3379757f..921595b5 100644 --- a/docs/manual/howto/htaccess.html.fr +++ b/docs/manual/howto/htaccess.html.fr @@ -44,7 +44,7 @@ Includes - SSI)

Les règles de réécriture dans les fichiers .htaccess

Exemple de CGI

Résolution des problèmes

Commentaires

Voir aussi

Commentaires

Fichiers .htaccess

@@ -304,7 +304,7 @@ Includes - SSI) </Directory> <Location "/"> - Options +IncludesNoExec -ExecCGI
+ Options +IncludesNoExec -ExecCGI </Location> diff --git a/docs/manual/howto/htaccess.html.ja.utf8 b/docs/manual/howto/htaccess.html.ja.utf8 index a7267632..73f495d4 100644 --- a/docs/manual/howto/htaccess.html.ja.utf8 +++ b/docs/manual/howto/htaccess.html.ja.utf8 @@ -45,7 +45,7 @@

SSI ã®ä¾‹

CGI ã®ä¾‹

å•é¡Œè§£æ±º

ã‚³ãƒ¡ãƒ³ãƒˆ

å‚ç…§

ã‚³ãƒ¡ãƒ³ãƒˆ

.htaccess ãƒ•ã‚¡ã‚¤ãƒ«

diff --git a/docs/manual/howto/htaccess.html.ko.euc-kr b/docs/manual/howto/htaccess.html.ko.euc-kr index d1febef8..6469c8fe 100644 --- a/docs/manual/howto/htaccess.html.ko.euc-kr +++ b/docs/manual/howto/htaccess.html.ko.euc-kr @@ -44,7 +44,7 @@

Server Side Includes ¿¹Á¦

CGI ¿¹Á¦

¹®Á¦ÇØ°á

Comments

Âü°í

Comments

.htaccess ÆÄÀÏ

diff --git a/docs/manual/howto/htaccess.html.pt-br b/docs/manual/howto/htaccess.html.pt-br index d1e23471..8de77e9d 100644 --- a/docs/manual/howto/htaccess.html.pt-br +++ b/docs/manual/howto/htaccess.html.pt-br @@ -43,7 +43,7 @@

Exemplo de Server Side Includes

Exemplo de CGI

Resolvendo Problemas

Comentários

Veja também

Comentários

Arquivos .htaccess

diff --git a/docs/manual/howto/http2.html b/docs/manual/howto/http2.html new file mode 100644 index 00000000..7e5de6d3 --- /dev/null +++ b/docs/manual/howto/http2.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: http2.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/howto/http2.html.en b/docs/manual/howto/http2.html.en new file mode 100644 index 00000000..94f2e11f --- /dev/null +++ b/docs/manual/howto/http2.html.en @@ -0,0 +1,277 @@ + + + + + +HTTP/2 guide - Apache HTTP Server Version 2.4 + + + + + + + +

+Apache > HTTP Server > Documentation > Version 2.4 > How-To / Tutorials

HTTP/2 guide

Available Languages: en | + fr | + ja | + ko | + tr

+ +

This is the howto guide for the HTTP/2 implementation in Apache httpd. This + feature is experimental and you may expect interfaces and directives to + change between releases. +

The HTTP/2 protocol
HTTP/2 in Apache httpd
Build httpd with HTTP/2 support
Basic Configuration
Clients
Useful tools to debug HTTP/2
Server Push

The HTTP/2 protocol

+ +

HTTP/2 is the evolution of the world's most successful application layer protocol, HTTP. + It focuses on making more efficient use of network resources. It does not change the fundamentals + of HTTP, the semantics. There are still request and responses and headers and all that. So, if + you already know HTTP/1, you know 95% about HTTP/2 as well.

There has been a lot written about HTTP/2 and how it works. The most normative is, of course, + its RFC 7540 + (also available in more readable formatting, YMMV). + So, there you'll find the nuts and bolts.

But, as RFC do, it's not really a good thing to read first. It's better to first understand + what a thing wants to do and then read the RFC about how it is done. A much + better document to start with is http2 explained + by Daniel Stenberg, the author of curl. It is available in + an ever growing list of languages, too!

Too Long, Didn't read: there are some new terms and gotchas that need to be kept in mind while reading this document:

HTTP/2 is a binary protocol, as opposed to HTTP 1.1 that is plain text. The latter is meant to be human readable (for example sniffing network traffic) meanwhile the former is not. More info in the official FAQ question.
h2 is HTTP/2 over TLS (protocol negotiation via ALPN).
h2c is HTTP/2 over TCP.
A frame is the smallest unit of communication within an HTTP/2 connection, consisting of a header and a variable-length sequence of octets structured according to the frame type. More info in the official documentation section.
A stream is a bidirectional flow of frames within the HTTP/2 connection. The correspondent concept in HTTP 1.1 is a request/response message exchange. More info in the official documentation section.
HTTP/2 is able to run multiple streams of data over the same TCP connection, avoiding the classic HTTP 1.1 head of blocking slow request and avoiding to re-instantiate TCP connections for each request/response (KeepAlive patched the problem in HTTP 1.1 but did not fully solve it).

HTTP/2 in Apache httpd

+ +

The HTTP/2 protocol is implemented by its own httpd module, aptly named + mod_http2. It implements the complete set + of features described by RFC 7540 and supports HTTP/2 over cleartext (http:), as + well as secure (https:) connections. The cleartext variant is named 'h2c', + the secure one 'h2'. For h2c it allows the direct + mode and the Upgrade: via an initial HTTP/1 request.

One feature of HTTP/2 that offers new capabilities for web developers is + Server Push. See that section on how your web application + can make use of it.

Build httpd with HTTP/2 support

+ +

mod_http2 uses the library of nghttp2 + as its implementation base. In order to build mod_http2 you need at least version 1.2.1 of + libnghttp2 installed on your system.

When you ./configure you Apache httpd source tree, you need to give it + '--enable-http2' as additional argument to trigger the build of the module. + Should your libnghttp2 reside in an unusual place (whatever that is on your + operating system), you may announce its location with '--with-nghttp2=<path>' + to configure.

While that should do the trick for most, they are people who might prefer a statically + linked nghttp2 in this module. For those, the option --enable-nghttp2-staticlib-deps + exists. It works quite similar to how one statically links openssl to mod_ssl.

Speaking of SSL, you need to be aware that most browsers will speak HTTP/2 only on https: + URLs, so you need a server with SSL support. But not only that, you will need a SSL library + that supports the ALPN extension. If OpenSSL is the library you use, you need + at least version 1.0.2.

Basic Configuration

+ + +

When you have a httpd built with mod_http2 you need some + basic configuration for it becoming active. The first thing, as with every Apache module, + is that you need to load it:

LoadModule http2_module modules/mod_http2.so

+ + +

The second directive you need to add to your server configuration is

Protocols h2 http/1.1

+ +

This allows h2, the secure variant, to be the preferred protocol on your server + connections. When you want to enable all HTTP/2 variants, you simply write:

Protocols h2 h2c http/1.1

+ +

Depending on where you put this directive, it affects all connections or just + the ones to a certain virtual host. You can nest it, as in:

Protocols http/1.1
+<VirtualHost ...>
+    ServerName test.example.org
+    Protocols h2 http/1.1
+</VirtualHost>

+ + +

This allows only HTTP/1 on connections, except SSL connections to test.example.org + which offer HTTP/2.

Choose a strong SSLCipherSuite

The SSLCipherSuite needs to be configured with a strong TLS cipher suite. The current version of mod_http2 does not enforce any cipher but most clients do so. Pointing a browser to a h2 enabled server with a inappropriate cipher suite will force it to simply refuse and fall back to HTTP 1.1. This is a common mistake that is done while configuring httpd for HTTP/2 the first time, so please keep it in mind to avoid long debugging sessions! If you want to be sure about the cipher suite to choose please avoid the ones listed in the HTTP/2 TLS blacklist.

The order of protocols mentioned is also relevant. By default, the first one is the + most preferred protocol. When a client offers multiple choices, the one most to the + left is selected. In

Protocols http/1.1 h2

+ +

the most preferred protocol is HTTP/1 and it will always be selected unless a + client only supports h2. Since we want to talk HTTP/2 to clients that + support it, the better order is

Protocols h2 h2c http/1.1

+ + +

There is one more thing to ordering: the client has its own preferences, too. If + you want, you can configure your server to select the protocol most preferred by + the client:

ProtocolsHonorOrder Off

+ +

makes the order you wrote the Protocols irrelevant and only the client's + ordering will decide.

A last thing: the protocols you configure are not checked for correctness + or spelling. You can mention protocols that do not exist, so there is no need + to guard Protocols with any IfModule checks.

For more advanced tips on configuration, see the + modules section about dimensioning and + how to manage multiple hosts with the same certificate.

Clients

+ +

Almost all modern browsers support HTTP/2, but only over SSL connections: Firefox (v43), + Chrome (v45), Safari (since v9), iOS Safari (v9), Opera (v35), Chrome for Android (v49) + and Internet Explorer (v11 on Windows10) (source).

Other clients, as well as servers, are listed + on the Implementations wiki, + among them implementations for c, c++, common lisp, dart, erlang, haskell, java, nodejs, php, + python, perl, ruby, rust, scala and swift.

Several of the non-browser client implementations support HTTP/2 over cleartext, h2c. The + most versatile being curl.

Useful tools to debug HTTP/2

+ +

The first tool to mention is of course curl. Please make sure that + your version supports HTTP/2 checking its Features:

    $ curl -V
+    curl 7.45.0 (x86_64-apple-darwin15.0.0) libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8 nghttp2/1.3.4
+    Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 [...] 
+    Features: IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP HTTP2
+

+ +

Mac OS homebrew notes

+ brew install curl --with-openssl --with-nghttp2 +

And for really deep inspection wireshark.

The nghttp2 package also includes clients, such as:

nghttp - useful to visualize the HTTP/2 frames and get a better idea of the protocol.
h2load - useful to stress-test your server.

Chrome offers detailed HTTP/2 logs on its connections via the + special net-internals page. There is also an interesting extension for Chrome and Firefox to visualize when your browser is using HTTP/2.

Server Push

+ +

The HTTP/2 protocol allows the server to PUSH responses to a client it never + asked for. The tone of the conversation is: "here is a request that you + never sent and the response to it will arrive soon..."

But there are restrictions: the client can disable this feature and the + server may only ever PUSH on a request that came from the client.

The intention is to allow the server to send resources to the client that + it will most likely need: a css or javascript resource that belongs to a html + page the client requested. A set of images that is referenced by a css, etc.

The advantage for the client is that it saves the time to send the request which + may range from a few milliseconds to half a second, depending on where on the + globe both are located. The disadvantage is that the client may get sent + things it already has in its cache. Sure, HTTP/2 allows for the early cancellation + of such requests, but still there are resources wasted.

To summarize: there is no one good strategy on how to make best use of this + feature of HTTP/2 and everyone is still experimenting. So, how do you experiment + with it in Apache httpd?

mod_http2 inspect response header for Link headers + in a certain format:

Link </xxx.css>;rel=preload, </xxx.js>; rel=preload

+ +

If the connection supports PUSH, these two resources will be sent to the + client. As a web developer, you may set these headers either directly in + your application response or you configure the server via

<Location /xxx.html>
+    Header add Link "</xxx.css>;rel=preload"
+    Header add Link "</xxx.js>;rel=preload"
+</Location>

+ +

If you want to use preload links without triggering a PUSH, you + can use the nopush parameter, as in

Link </xxx.css>;rel=preload;nopush

+ +

or you may disable PUSHes for your server entirely with the directive

H2Push Off

+ +

And there is more:

The module will keep a diary of what has been PUSHed for each connection + (hashes of URLs, basically) and will not PUSH the same resource twice. When + the connection closes, this information is discarded.

There are people thinking about how a client can tell a server what it + already has, so PUSHes for those things can be avoided, but this is all + highly experimental right now.

Another experimental draft that has been implemented in mod_http2 + is the + Accept-Push-Policy Header Field where a client can, for each request, define + what kind of PUSHes it accepts.

Available Languages: en | + fr | + ja | + ko | + tr

Comments

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.

+ \ No newline at end of file diff --git a/docs/manual/howto/index.html.en b/docs/manual/howto/index.html.en index 71f33a6f..5ca462ab 100644 --- a/docs/manual/howto/index.html.en +++ b/docs/manual/howto/index.html.en @@ -87,6 +87,20 @@ +

HTTP/2 with httpd

HTTP/2 is the evolution of the world's most successful application layer protocol, HTTP. + It focuses on making more efficient use of network resources without changing the semantics of HTTP. + This guide explains how HTTP/2 is implemented in httpd, showing basic configurations tips and + best practices. +

+ +

See: HTTP/2 guide

+ +

Introduction to Server Side Includes: diff --git a/docs/manual/howto/index.html.fr b/docs/manual/howto/index.html.fr index f55266c3..d7ecd7a9 100644 --- a/docs/manual/howto/index.html.fr +++ b/docs/manual/howto/index.html.fr @@ -90,6 +90,21 @@

HTTP/2 avec httpd

HTTP/2 est une évolution du protocole de la couche application le plus + connu au monde, HTTP. Les efforts se sont concentrés sur une amélioration + de l'efficacité de l'utilisation des ressources réseau sans modifier la + sémantique de HTTP. Ce guide explique la manière dont HTTP/2 est + implémenté dans httpd, donne des conseils pour une configuration de base + ainsi qu'une liste de recommandations. +

+ +

Voir le guide HTTP/2

Introduction au Inclusions côté Serveur (Server Side Includes ou SSI)

Per-user web directories
Setting the file path with UserDir
Enabling a cgi directory for each user
Allowing users to alter configuration

Per-user web directories

@@ -139,8 +139,8 @@ You can, likewise, disable the feature for all but a few users by using a configuration like the following:

      UserDir disabled

-      UserDir enabled rbowen krietz

UserDir disabled
+UserDir enabled rbowen krietz

See UserDir diff --git a/docs/manual/howto/public_html.html.fr b/docs/manual/howto/public_html.html.fr index 8f4cb852..82acfb9a 100644 --- a/docs/manual/howto/public_html.html.fr +++ b/docs/manual/howto/public_html.html.fr @@ -40,15 +40,15 @@ la directive U

Notez que par défaut, l'accès à ces répertoires n'est pas permis. Vous pouvez en permettre l'accès à l'aide de la directive UserDir en -décommentant la ligne


-    
-      #Include conf/extra/httpd-userdir.conf
-    
+décommentant la ligne :
+    #Include conf/extra/httpd-userdir.conf
+
     dans le fichier de configuration par défaut
     conf/httpd.conf, et en adaptant le
     fichier httpd-userdir.conf selon vos besoins, ou en
     incluant les directives appropriées dans une section
-    Directory du fichier de configuration principal.
+    <Directory> du fichier de
+    configuration principal.


  Répertoires web utilisateurs
  Définition du chemin des fichiers avec UserDir
@@ -59,7 +59,7 @@ d
  Permettre aux utilisateurs de modifier la
     configuration
 
Voir aussi
Mise en correspondance des URLs
-avec le système de fichiers
Commentaires
+avec le système de fichiersCommentaires
 
 
 Répertoires web utilisateurs
@@ -153,8 +153,8 @@ avec le syst
     utilisateurs sauf certains d'entre eux en utilisant une
     configuration du style :
 
-          UserDir disabled

-      UserDir enabled rbowen krietz
+    UserDir disabled
+UserDir enabled rbowen krietz
 
 
     Vous trouverez d'autres exemples dans la documentation de
diff --git a/docs/manual/howto/public_html.html.ja.utf8 b/docs/manual/howto/public_html.html.ja.utf8
index 5dd97e16..75d3b90d 100644
--- a/docs/manual/howto/public_html.html.ja.utf8
+++ b/docs/manual/howto/public_html.html.ja.utf8
@@ -61,7 +61,7 @@
 
 ã“ã®æ©Ÿèƒ½ã‚’ä½¿ç”¨ã§ãã‚‹ãƒ¦ãƒ¼ã‚¶ã‚’åˆ¶é™ã™ã‚‹
  ãƒ¦ãƒ¼ã‚¶æ¯Žã® CGI ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒª
  ãƒ¦ãƒ¼ã‚¶ã«ã‚ˆã‚‹è¨å®šå¤‰æ›´ã‚’è¨±å¯
-å‚ç…§
URL ã‹ã‚‰ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ ã¸ã®ãƒžãƒƒãƒ”ãƒ³ã‚°
ã‚³ãƒ¡ãƒ³ãƒˆ
+å‚ç…§
URL ã‹ã‚‰ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ ã¸ã®ãƒžãƒƒãƒ”ãƒ³ã‚°
ã‚³ãƒ¡ãƒ³ãƒˆ
 
 
 ãƒ¦ãƒ¼ã‚¶æ¯Žã®ã‚¦ã‚§ãƒ–ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒª
diff --git a/docs/manual/howto/public_html.html.ko.euc-kr b/docs/manual/howto/public_html.html.ko.euc-kr
index c74e6a49..bdd80af7 100644
--- a/docs/manual/howto/public_html.html.ko.euc-kr
+++ b/docs/manual/howto/public_html.html.ko.euc-kr
@@ -44,7 +44,7 @@
  ±â´ÉÀ» ÀÌ¿ëÇÒ »ç¿ëÀÚ Á¦ÇÑÇÏ±â
  °¢ »ç¿ëÀÚº° cgi µð·ºÅä¸® ÁöÁ¤ÇÏ±â
  »ç¿ëÀÚ°¡ ¼³Á¤À» º¯°æÇÒ ¼ö ÀÖµµ·Ï ¸¸µé±â
-Âü°í
URLÀ» ÆÄÀÏ½Ã½ºÅÛ¿¡ ´ëÀÀ
Comments
+Âü°í
URLÀ» ÆÄÀÏ½Ã½ºÅÛ¿¡ ´ëÀÀ
Comments
 
 
 »ç¿ëÀÚº° À¥µð·ºÅä¸®
diff --git a/docs/manual/howto/public_html.html.tr.utf8 b/docs/manual/howto/public_html.html.tr.utf8
index e333e8e1..cc9b8e91 100644
--- a/docs/manual/howto/public_html.html.tr.utf8
+++ b/docs/manual/howto/public_html.html.tr.utf8
@@ -29,6 +29,7 @@
  ko  |
  tr 
 
+Bu Ã§eviri gÃ¼ncel olmayabilir. Son deÄŸiÅŸiklikler iÃ§in Ä°ngilizce sÃ¼rÃ¼m geÃ§erlidir.
 
   Ã‡ok kullanÄ±cÄ±lÄ± sistemlerde, UserDir yÃ¶nergesi ile her kullanÄ±cÄ±nÄ±n kendi ev dizininde
     bir sitesi olmasÄ± saÄŸlanabilir.
@@ -57,7 +58,7 @@
 
 Her kullanÄ±cÄ±ya bir CGI dizini tahsis etmek
  KullanÄ±cÄ±larÄ±n yapÄ±landÄ±rmayÄ± deÄŸiÅŸtirmesine izin vermek
 AyrÄ±ca bakÄ±nÄ±z:
URLâ€™lerin Dosya Sistemi ile
-  EÅŸleÅŸtirilmesi
Yorum
+  EÅŸleÅŸtirilmesiYorum
 
 
 KullanÄ±cÄ± sayfalarÄ± dizinleri
diff --git a/docs/manual/howto/reverse_proxy.html.en b/docs/manual/howto/reverse_proxy.html.en
index 12d1593f..ea76471f 100644
--- a/docs/manual/howto/reverse_proxy.html.en
+++ b/docs/manual/howto/reverse_proxy.html.en
@@ -63,7 +63,7 @@
  Balancer Manager
  Dynamic Health Checks
  BalancerMember status flags
-Comments
+See also
Comments
 
 
 Reverse Proxy
@@ -119,7 +119,7 @@ ProxyPassReverse "/images"  "http://www.example.com/"
       requests and for the reverse proxy to load balance and failover among
       them. This group is sometimes called a cluster but Apache httpd's
       term is a balancer. One defines a balancer by leveraging the
-      Proxy and
+      <Proxy> and
       BalancerMember directives as
       shown:
     
@@ -235,7 +235,7 @@ ProxyPassReverse "/images/"  "balancer://myset/"
 
 
     Warning
-      Do not enable the balancer-manager until you have secured your server. In
+      
Do not enable the balancer-manager until you have secured your server. In
       particular, ensure that access to the URL is tightly
       restricted.
     
diff --git a/docs/manual/howto/ssi.html.en b/docs/manual/howto/ssi.html.en
index fddc7c68..9327ed66 100644
--- a/docs/manual/howto/ssi.html.en
+++ b/docs/manual/howto/ssi.html.en
@@ -41,7 +41,7 @@ existing HTML documents.
  Executing commands
  Advanced SSI techniques
  Conclusion
-Comments
+See also
Comments
 
 
 Introduction
@@ -109,8 +109,8 @@ existing HTML documents.
     do this. You can tell Apache to parse any file with a
     particular file extension, such as .shtml, with
     the following directives:
-        AddType text/html .shtml

-        AddOutputFilter INCLUDES .shtml
+AddType text/html .shtml
+AddOutputFilter INCLUDES .shtml
 
 
     One disadvantage to this approach is that if you wanted to
diff --git a/docs/manual/howto/ssi.html.fr b/docs/manual/howto/ssi.html.fr
index a2670983..a53b8bad 100644
--- a/docs/manual/howto/ssi.html.fr
+++ b/docs/manual/howto/ssi.html.fr
@@ -43,7 +43,7 @@ HTML pr
 
 Exécution de commandes
  Techniques SSI avancées
  Conclusion
-Commentaires
+Voir aussi
Commentaires
 
 
 Introduction
@@ -117,8 +117,8 @@ HTML pr
     directives SSI. Vous devez indiquer à Apache quels fichiers seront
     concernés. Vous pouvez y parvenir en indiquant une extension, comme
     .shtml, à l'aide des directives suivantes :
-        AddType text/html .shtml

-        AddOutputFilter INCLUDES .shtml
+AddType text/html .shtml
+AddOutputFilter INCLUDES .shtml
 
 
     Un des désavantages de cette approche réside dans le fait que si
diff --git a/docs/manual/howto/ssi.html.ja.utf8 b/docs/manual/howto/ssi.html.ja.utf8
index dc10ddcd..326f1332 100644
--- a/docs/manual/howto/ssi.html.ja.utf8
+++ b/docs/manual/howto/ssi.html.ja.utf8
@@ -45,7 +45,7 @@
 
 ã‚³ãƒžãƒ³ãƒ‰ã®å®Ÿè¡Œ
  é«˜åº¦ãª SSI ãƒ†ã‚¯ãƒ‹ãƒƒã‚¯
  çµ‚ã‚ã‚Šã«
-ã‚³ãƒ¡ãƒ³ãƒˆ
+å‚ç…§
ã‚³ãƒ¡ãƒ³ãƒˆ
 
 
 ã¯ã˜ã‚ã«
diff --git a/docs/manual/howto/ssi.html.ko.euc-kr b/docs/manual/howto/ssi.html.ko.euc-kr
index ed04e795..1f720e94 100644
--- a/docs/manual/howto/ssi.html.ko.euc-kr
+++ b/docs/manual/howto/ssi.html.ko.euc-kr
@@ -43,7 +43,7 @@
  ¸í·É¾î ½ÇÇàÇÏ±â
  °í±Þ SSI ±â¹ý
  °á·Ð
-Comments
+Âü°í
Comments
 
 
 ¼Ò°³
-- 
cgit v1.2.3

See also

Voir aussi

See also

Note

Voir aussi

Note

å‚ç…§

Âü°í

AyrÄ±ca bakÄ±nÄ±z:

See also

Voir aussi

å‚ç…§

Âü°í

See also

Voir aussi

å‚ç…§

Âü°í

Veja também

HTTP/2 guide

See also

Choose a strong SSLCipherSuite

Mac OS homebrew notes

See also

See also

Voir aussi

å‚ç…§

å‚ç…§

Âü°í

Âü°í

AyrÄ±ca bakÄ±nÄ±z:

See also

Warning

See also

Voir aussi

å‚ç…§

Âü°í

å‚ç…§

å‚ç…§

å‚ç…§

å‚ç…§

å‚ç…§

å‚ç…§