1
0
mirror of https://github.com/apache/httpd.git synced 2026-01-06 09:01:14 +03:00
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1381546 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Daniel Gruno
2012-09-06 09:46:27 +00:00
parent 140436f08f
commit b8a0349422
7 changed files with 42 additions and 44 deletions

View File

@@ -311,7 +311,7 @@ of clients</td></tr>
the amount of shared memory, that will be allocated at the server
startup for keeping track of clients. Note that the shared memory
segment cannot be set less than the space that is necessary for
tracking at least <em>one</em> client. This value is dependant on your
tracking at least <em>one</em> client. This value is dependent on your
system. If you want to find out the exact value, you may simply
set <code class="directive">AuthDigestShmemSize</code> to the value of
<code>0</code> and read the error message after trying to start the

View File

@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
<!-- English Revision : 1371585 -->
<!-- English Revision: 1371585:1380533 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->

View File

@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
<!-- English Revision: 105989:1371585 (outdated) -->
<!-- English Revision: 105989:1380533 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more

View File

@@ -8,7 +8,7 @@
<variants>
<variant>en</variant>
<variant>fr</variant>
<variant outdated="yes">fr</variant>
<variant outdated="yes">ko</variant>
</variants>
</metafile>

View File

@@ -149,13 +149,14 @@ SessionCryptoPassphrase secret
directive. Typically this login page will contain an HTML form, asking the user to
provide their usename and password.</p>
<div class="example"><h3>Example login form</h3><p><code>
&lt;form method="POST" action="/dologin.html"&gt;<br />
Username: &lt;input type="text" name="httpd_username" value="" /&gt;<br />
Password: &lt;input type="password" name="httpd_password" value="" /&gt;<br />
&lt;input type="submit" name="login" value="Login" /&gt;<br />
&lt;/form&gt;<br />
</code></p></div>
<div class="example"><h3>Example login form</h3><pre class="prettyprint lang-html">
&lt;form method="POST" action="/dologin.html"&gt;
Username: &lt;input type="text" name="httpd_username" value="" /&gt;
Password: &lt;input type="password" name="httpd_password" value="" /&gt;
&lt;input type="submit" name="login" value="Login" /&gt;
&lt;/form&gt;
</pre>
</div>
<p>The part that does the actual login is handled by the <var>form-login-handler</var>.
The action of the form should point at this handler, which is configured within
@@ -187,16 +188,15 @@ SessionCryptoPassphrase secret
form, as in the example below. As a result, the same <var>form-login-handler</var> can be
reused for different areas of a website.</p>
<div class="example"><h3>Example login form with location</h3><p><code>
&lt;form method="POST" action="/dologin.html"&gt;<br />
<span class="indent">
Username: &lt;input type="text" name="httpd_username" value="" /&gt;<br />
Password: &lt;input type="password" name="httpd_password" value="" /&gt;<br />
&lt;input type="submit" name="login" value="Login" /&gt;<br />
&lt;input type="hidden" name="httpd_location" value="http://example.com/success.html" /&gt;<br />
</span>
&lt;/form&gt;<br />
</code></p></div>
<div class="example"><h3>Example login form with location</h3><pre class="prettyprint lang-html">
&lt;form method="POST" action="/dologin.html"&gt;
Username: &lt;input type="text" name="httpd_username" value="" /&gt;
Password: &lt;input type="password" name="httpd_password" value="" /&gt;
&lt;input type="submit" name="login" value="Login" /&gt;
&lt;input type="hidden" name="httpd_location" value="http://example.com/success.html" /&gt;
&lt;/form&gt;
</pre>
</div>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
@@ -245,15 +245,14 @@ SessionCryptoPassphrase secret
the original protected URL, without the page having to know what that
URL is.</p>
<div class="example"><h3>Example inline login form</h3><p><code>
&lt;form method="POST" <strong>action=""</strong>&gt;<br />
<span class="indent">
Username: &lt;input type="text" name="httpd_username" value="" /&gt;<br />
Password: &lt;input type="password" name="httpd_password" value="" /&gt;<br />
&lt;input type="submit" name="login" value="Login" /&gt;<br />
</span>
&lt;/form&gt;<br />
</code></p></div>
<div class="example"><h3>Example inline login form</h3><pre class="prettyprint lang-html">
&lt;form method="POST" <strong>action=""</strong>&gt;
Username: &lt;input type="text" name="httpd_username" value="" /&gt;
Password: &lt;input type="password" name="httpd_password" value="" /&gt;
&lt;input type="submit" name="login" value="Login" /&gt;
&lt;/form&gt;
</pre>
</div>
<p>When the end user has filled in their login details, the form will make
an HTTP POST request to the original password protected URL.
@@ -281,18 +280,17 @@ SessionCryptoPassphrase secret
<p>To enable body preservation, add three additional fields to the login form as
per the example below.</p>
<div class="example"><h3>Example with body preservation</h3><p><code>
&lt;form method="POST" action=""&gt;<br />
<span class="indent">
Username: &lt;input type="text" name="httpd_username" value="" /&gt;<br />
Password: &lt;input type="password" name="httpd_password" value="" /&gt;<br />
&lt;input type="submit" name="login" value="Login" /&gt;<br />
<strong>&lt;input type="hidden" name="httpd_method" value="POST" /&gt;<br />
&lt;input type="hidden" name="httpd_mimetype" value="application/x-www-form-urlencoded" /&gt;<br />
&lt;input type="hidden" name="httpd_body" value="name1=value1&amp;name2=value2" /&gt;</strong><br />
</span>
&lt;/form&gt;
</code></p></div>
<div class="example"><h3>Example with body preservation</h3><pre class="prettyprint lang-html">
&lt;form method="POST" action=""&gt;
Username: &lt;input type="text" name="httpd_username" value="" /&gt;
Password: &lt;input type="password" name="httpd_password" value="" /&gt;
&lt;input type="submit" name="login" value="Login" /&gt;
<br /> <strong>&lt;input type="hidden" name="httpd_method" value="POST" /&gt;
&lt;input type="hidden" name="httpd_mimetype" value="application/x-www-form-urlencoded" /&gt;
&lt;input type="hidden" name="httpd_body" value="name1=value1&amp;name2=value2" /&gt;</strong><br />
&lt;/form&gt;
</pre>
</div>
<p>How the method, mimetype and body of the original request are embedded within the
login form will depend on the platform and technology being used within the website.

View File

@@ -727,7 +727,7 @@ connection client certificates.</td></tr>
<p>It specifies the directory path, file name or nickname of a
per connection client certificate used when establishing an SSL
or TLS connection to an LDAP server. Different locations or
directories may have their own independant client certificate
directories may have their own independent client certificate
settings. Some LDAP toolkits (notably Novell)
do not support per connection client certificates, and will throw an
error on LDAP server connection if you try to use this directive

View File

@@ -1,7 +1,7 @@
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
<!-- English Revision: 1358946:1371684 (outdated) -->
<!-- English Revision: 1358946:1380533 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->