base

2026-08-07 17:38:18 +09:00
commit 873193a243
9613 changed files with 2755992 additions and 0 deletions
@@ -0,0 +1,60 @@
+<refentry id="refreqopts">
+
+  <refmeta>
+    <refentrytitle>ne_set_request_expect100</refentrytitle>
+    <manvolnum>3</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname id="ne_set_request_expect100">ne_set_request_expect100</refname>
+    <refpurpose>function to enable Expect: 100-continue support</refpurpose>
+  </refnamediv>
+  
+  <refsynopsisdiv>
+
+    <funcsynopsis>
+
+      <funcsynopsisinfo>#include &lt;ne_request.h&gt;</funcsynopsisinfo>
+
+      <funcprototype>
+        <funcdef>void <function>ne_set_request_expect100</function></funcdef>
+        <paramdef>ne_request *<parameter>request</parameter></paramdef>
+        <paramdef>int <parameter>flag</parameter></paramdef>
+      </funcprototype>
+
+    </funcsynopsis>
+
+  </refsynopsisdiv>
+
+  <refsect1>
+    <title>Description</title>
+
+    <para>An extension introduced in the HTTP/1.1 specification was
+    the use of the <literal>Expect: 100-continue</literal> header.
+    This header allows an HTTP client to be informed of the expected
+    response status before the request message body is sent: a useful
+    optimisation for situations where a large message body is to be
+    sent.  The <function>ne_set_request_expect100</function> function
+    can be used to enable this feature by passing the
+    <parameter>flag</parameter> parameter as any non-zero
+    integer.</para>
+
+    <warning><para>Unfortunately, if this header is sent to a server
+    which is not fully compliant with the HTTP/1.1 specification, a
+    deadlock occurs resulting in a temporarily "hung" connection.
+    neon will recover gracefully from this situation, but only after a
+    15 second timeout.  It is highly recommended that this option is
+    not enabled unless it is known that the server in use correctly
+    implements <literal>Expect: 100-continue</literal>
+    support.</para></warning>
+
+  </refsect1>
+
+  <refsect1>
+    <title>See also</title>
+
+    <para><xref linkend="ne_request_create"/>.</para>
+
+  </refsect1>
+
+</refentry>