1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
3<html><head>
4<title>CURLOPT_POSTREDIR man page</title>
5<meta name="generator" content="roffit">
6<STYLE type="text/css">
7P.level0 {
8 padding-left: 2em;
9}
10
11P.level1 {
12 padding-left: 4em;
13}
14
15P.level2 {
16 padding-left: 6em;
17}
18
19span.emphasis {
20 font-style: italic;
21}
22
23span.bold {
24 font-weight: bold;
25}
26
27span.manpage {
28 font-weight: bold;
29}
30
31h2.nroffsh {
32 background-color: #e0e0e0;
33}
34
35span.nroffip {
36 font-weight: bold;
37 font-size: 120%;
38 font-family: monospace;
39}
40
41p.roffit {
42 text-align: center;
43 font-size: 80%;
44}
45</STYLE>
46</head><body>
47
48<p class="level0"><a name="NAME"></a><h2 class="nroffsh">NAME</h2>
49<p class="level0">CURLOPT_POSTREDIR - how to act on a HTTP POST redirect <a name="SYNOPSIS"></a><h2 class="nroffsh">SYNOPSIS</h2>
50<p class="level0"><pre>
51<p class="level0">#include &lt;curl/curl.h&gt;
52 <p class="level0">CURLcode curl_easy_setopt(CURL *handle, CURLOPT_POSTREDIR,
53 &nbsp;                         long bitmask);
54 </pre>
55<a name="DESCRIPTION"></a><h2 class="nroffsh">DESCRIPTION</h2>
56<p class="level0">Pass a bitmask to control how libcurl acts on redirects after POSTs that get a 301, 302 or 303 response back.  A parameter with bit 0 set (value <span Class="bold">CURL_REDIR_POST_301</span>) tells the library to respect <a href="http://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>/10.3.2 and not convert POST requests into GET requests when following a 301 redirection. Setting bit 1 (value <span Class="bold">CURL_REDIR_POST_302</span>) makes libcurl maintain the request method after a 302 redirect whilst setting bit 2 (value <span Class="bold">CURL_REDIR_POST_303</span>) makes libcurl maintain the request method after a 303 redirect. The value <span Class="bold">CURL_REDIR_POST_ALL</span> is a convenience define that sets all three bits. 
57<p class="level0">The non-RFC behaviour is ubiquitous in web browsers, so the library does the conversion by default to maintain consistency. However, a server may require a POST to remain a POST after such a redirection. This option is meaningful only when setting <a Class="emphasis" href="/CURLOPT_FOLLOWLOCATION.html">CURLOPT_FOLLOWLOCATION</a>. <a name="DEFAULT"></a><h2 class="nroffsh">DEFAULT</h2>
58<p class="level0">0 <a name="PROTOCOLS"></a><h2 class="nroffsh">PROTOCOLS</h2>
59<p class="level0">HTTP <a name="EXAMPLE"></a><h2 class="nroffsh">EXAMPLE</h2>
60<p class="level0">TODO <a name="AVAILABILITY"></a><h2 class="nroffsh">AVAILABILITY</h2>
61<p class="level0">Added in 7.17.1. This option was known as CURLOPT_POST301 up to 7.19.0 as it only supported the 301 then. <a name="RETURN"></a><h2 class="nroffsh">RETURN VALUE</h2>
62<p class="level0">Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not. <a name="SEE"></a><h2 class="nroffsh">SEE ALSO</h2>
63<p class="level0"><a Class="manpage" href="/CURLOPT_FOLLOWLOCATION.html">CURLOPT_FOLLOWLOCATION</a> <a Class="manpage" href="/CURLOPT_POSTFIELDS.html">CURLOPT_POSTFIELDS</a> <span Class="manpage"> </span> <p class="roffit">
64 This HTML page was made with <a href="http://daniel.haxx.se/projects/roffit/">roffit</a>.
65</body></html>
66