You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2003/01/05 23:11:13 UTC
cvs commit: httpd-docs-1.3/htdocs/manual content-negotiation.html
nd 2003/01/05 14:11:13
Modified: htdocs/manual content-negotiation.html
Log:
fixed typos and added anchor id
Submitted by: Nobuyuki Morita <ma...@plum.freemail.ne.jp>
Revision Changes Path
1.28 +15 -15 httpd-docs-1.3/htdocs/manual/content-negotiation.html
Index: content-negotiation.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/content-negotiation.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- content-negotiation.html 14 Mar 2002 21:31:00 -0000 1.27
+++ content-negotiation.html 5 Jan 2003 22:11:13 -0000 1.28
@@ -414,18 +414,18 @@
dimensions of variance.</p>
<p>You should be aware that the error message returned by Apache is
- neccessarily rather terse and might confuse some users (even though it
- lists the available alternatives). If you want to avoid users seeing this
- error page, you should organize your documents such that a document in a
- default language (or with a default encoding etc.) is always returned if a
- document is not available in any of the languages, encodings etc. the
- browser asked for.</p>
-
- <p>In particular, if you want a document in a default language to
- be returned if a document is not available in any of the languages
- a browser asked for, you should create a document with no language
- attribute set. See <a href="#nolanguage">Variants with no
- Language</a> below for details.</p></li>
+ neccessarily rather terse and might confuse some users (even though it
+ lists the available alternatives). If you want to avoid users seeing this
+ error page, you should organize your documents such that a document in a
+ default language (or with a default encoding etc.) is always returned if a
+ document is not available in any of the languages, encodings etc. the
+ browser asked for.</p>
+
+ <p>In particular, if you want a document in a default language to
+ be returned if a document is not available in any of the languages
+ a browser asked for, you should create a document with no language
+ attribute set. See <a href="#nolanguage">Variants with no
+ Language</a> below for details.</p></li>
</ol>
<h2><a id="better" name="better">Fiddling with Quality
@@ -481,7 +481,7 @@
<em>not</em> applied, so requests from browsers which send the
correct information to start with work as expected.</p>
- <h3><a name="nolanguage">Variants with no Language</a></h3>
+ <h3><a id="nolanguage" name="nolanguage">Variants with no Language</a></h3>
<p>If some of the variants for a particular resource have a
language attribute, and some do not, those variants with no
@@ -493,7 +493,7 @@
variant which can be supplied if none of the other variants match
the browser's language preferences. This allows you to avoid users
seeing a "406" error page if their browser is set to only accept
- languages which you do not offer for the ressource that was
+ languages which you do not offer for the resource that was
requested.</p>
<p>For example, consider the situation with Multiviews enabled and
@@ -513,7 +513,7 @@
one of foo.en.html or foo.fr.html will be returned. If the browser
does not list either en or fr as acceptable, foo.html will be
returned instead. If the client requests <code>foo.html</code>
- instead, then no negotation will occur since the exact match
+ instead, then no negotiation will occur since the exact match
will be returned. To avoid this problem, it is sometimes helpful
to name the "no language" variant <code>foo.html.html</code> to assure
that Multiviews and language negotiation will come into play.</p>