summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoe <joe@61a7d7f5-40b7-0310-9c16-bb0ea8cb1845>2004-10-02 19:38:59 +0000
committerjoe <joe@61a7d7f5-40b7-0310-9c16-bb0ea8cb1845>2004-10-02 19:38:59 +0000
commit3283fd5d9bdc734fed8276dd4675833e02670cfe (patch)
tree51e55a698b4d698ff8835cd383661c964865897a /doc
parent08c4265e806d73805c51fa67b64aa33861740679 (diff)
downloadneon-3283fd5d9bdc734fed8276dd4675833e02670cfe.tar.gz
Merge trunk up to current neon CVS HEAD.
git-svn-id: http://svn.webdav.org/repos/projects/neon/trunk@256 61a7d7f5-40b7-0310-9c16-bb0ea8cb1845
Diffstat (limited to 'doc')
-rw-r--r--doc/biblio.xml9
-rw-r--r--doc/ref/clicert.xml6
-rw-r--r--doc/using.xml29
3 files changed, 32 insertions, 12 deletions
diff --git a/doc/biblio.xml b/doc/biblio.xml
index cda37a7..43574b8 100644
--- a/doc/biblio.xml
+++ b/doc/biblio.xml
@@ -10,12 +10,11 @@
<pubdate>March 2001</pubdate>
</biblioentry>
-<biblioentry id="bib.xsltrec">
+<biblioentry id="bib.xmlnames">
<abbrev>REC-XML-names</abbrev>
- <editor><firstname>James</firstname><surname>Clark</surname></editor>
- <title><ulink url="http://www.w3.org/TR/xslt">XSL Transformations
- (XSLT) Version 1.0</ulink></title> <publishername>W3C
- Recommendation</publishername> <pubdate>16 November 1999</pubdate>
+ <corpauthor>World Wide Web Consortium</corpauthor>
+ <title><ulink url="http://www.w3.org/TR/REC-xml-names">Namespaces in XML</ulink></title>
+ <pubdate>January 1999</pubdate>
</biblioentry>
<biblioentry id="bib.rfc2616">
diff --git a/doc/ref/clicert.xml b/doc/ref/clicert.xml
index 49f95cf..67833aa 100644
--- a/doc/ref/clicert.xml
+++ b/doc/ref/clicert.xml
@@ -62,9 +62,9 @@
<para>The <function>ne_ssl_clicert_read</function> function reads
a <firstterm>client certificate</firstterm> from a
PKCS#12-formatted file, and returns an
- <type>ne_ssl_client_certificate</type> object. If the client
+ <type>ne_ssl_client_cert</type> object. If the client
certificate is encrypted, it must be decrypted before it is used.
- An <type>ne_ssl_client_certificate</type> object holds a client
+ An <type>ne_ssl_client_cert</type> object holds a client
certificate and the associated private key, not just a
certificate; the term "<glossterm>client certificate</glossterm>"
will used to refer to this pair.</para>
@@ -124,7 +124,7 @@
<para>The following code reads a client certificate and decrypts
it if necessary, then loads it into an HTTP session.</para>
- <programlisting>ne_ssl_client_certificate *ccert;
+ <programlisting>ne_ssl_client_cert *ccert;
ccert = ne_ssl_clicert_read("/path/to/client.p12");
diff --git a/doc/using.xml b/doc/using.xml
index efb53d1..e88c9ef 100644
--- a/doc/using.xml
+++ b/doc/using.xml
@@ -73,11 +73,11 @@
</sect1>
<sect1 id="compliance">
- <title>Protocol compliance</title>
+ <title>Standards compliance</title>
- <para>&neon; is intended to be compliant with the IETF
- protocol standards it implements, with a few exceptions where
- real-world use has necessitated minor deviations. These
+ <para>&neon; is intended to be compliant with the IETF and W3C
+ standards which it implements, with a few exceptions due to
+ practical necessity or interoperability issues. These
exceptions are documented in this section.</para>
<sect2><title>RFC 2518, HTTP Extensions for Distributed Authoring&mdash;WebDAV</title>
@@ -116,4 +116,25 @@
quotes&mdash;this is not known to cause any problems with
other server implementations.</para></sect2>
+ <sect2>
+ <title>Namespaces in XML</title>
+
+ <para>The &neon; XML parser interface will accept and parse
+ without error some XML documents which are well-formed
+ according to the XML specification but do not conform to the
+ "Namespaces in XML" specification <xref
+ linkend="bib.xmlnames"/>. Specifically: the restrictions on
+ the first character of the <literal>NCName</literal> rule are
+ not all implemented; &neon; will allow any
+ <literal>CombiningChar</literal>, <literal>Extender</literal>
+ and some characters from the <literal>Digit</literal> class in
+ this position.</para> </sect2>
+
+ <!-- a few RFC2818/3280 issues: rules about when to cache
+ sessions in the face of unclean shutdown are strict, neon is
+ probably not compliant: document or fix. Likewise SSL
+ shutdown issues in general. Cert hostname checks allow
+ wildcard "*." syntax which is less than 2818 but more than
+ 3280 requires. -->
+
</sect1>