<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>ne_set_request_expect100</title><link rel="stylesheet" href="../manual.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="neon HTTP/WebDAV client library"><link rel="up" href="ref.html" title="neon API reference"><link rel="prev" href="refopts.html" title="ne_set_useragent"><link rel="next" href="refreqbody.html" title="ne_set_request_body_buffer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">ne_set_request_expect100</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="refopts.html">Prev</a> </td><th width="60%" align="center">neon API reference</th><td width="20%" align="right"> <a accesskey="n" href="refreqbody.html">Next</a></td></tr></table><hr></div><div class="refentry" lang="en"><a name="refreqopts"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ne_set_request_expect100 — function to enable Expect: 100-continue support</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><pre class="funcsynopsisinfo">#include <ne_request.h></pre><table border="0" summary="Function synopsis" cellspacing="0" cellpadding="0"><tr><td><code class="funcdef">void <b class="fsfunc">ne_set_request_expect100</b>(</code></td><td>ne_request * </td><td><var class="pdparam">request</var>, </td></tr><tr><td> </td><td>int </td><td><var class="pdparam">flag</var><code>)</code>;</td></tr></table></div></div><div class="refsect1" lang="en"><a name="id2597395"></a><h2>Description</h2><p>An extension introduced in the HTTP/1.1 specification was
the use of the <code class="literal">Expect: 100-continue</code> 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 <code class="function">ne_set_request_expect100</code> function
can be used to enable this feature by passing the
<code class="parameter">flag</code> parameter as any non-zero
integer.</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>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 <code class="literal">Expect: 100-continue</code>
support.</p></div></div><div class="refsect1" lang="en"><a name="id2597448"></a><h2>See also</h2><p><a href="refreq.html#ne_request_create">ne_request_create</a>.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="refopts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ref.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="refreqbody.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">ne_set_useragent </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> ne_set_request_body_buffer</td></tr></table></div></body></html>
