PHP and cURL: Disabling 100-continue header
Published June 15th, 2006I’ve been using cURL (through PHP) to build a sort of proxy for a project I’m working on. I need to parse the returned headers (to recover the HTTP status), so had included a very simple script to do so. It had worked fine in the past, but for some reason barfed in this case. A closer look at what was being returned revealed that for some reason, Apache was prepending the ‘normal’ headers with an extra response header:
HTTP/1.1 100 Continue
HTTP/1.1 200 OK Date: Fri, 09 Jun 2006 15:23:42 GMT
Server: Apache
...A bit of Googling revealed that this was to do with a header that cURL sends by default:
Expect: 100-continue
…which in turns tells Apache to send the extra header. I poked around a fair bit but couldn’t quite find a workable solution short of manually removing the header in PHP, which seemed a bit clumsy. Finally, on a hunch I tried this:
curl_setopt( $curl_handle, CURLOPT_HTTPHEADER, array( 'Expect:' ) );
…which basically overrides the original ‘Expect:’ header with an empty one.
Hope this helps someone.
DeyV on December 3, 2006
It was very helpful.
many Thanks.
Murray McDonald on July 8, 2008
Good hunch! Saved me a lot of time. Thanks.
mike on August 13, 2008
This did help me. Thank you.
Lighttpd fails the request with an Expect: 100-continue header. Bleh. nginx had no problems
Matthom on December 29, 2008
This helped me out in a pinch! thanks!
Jono Sheppard on June 25, 2009
This helped – was trying to send a raw SOAP request but curl couldn’t move past the initial “continue” until I tried this. Thanks!
pawlak on July 6, 2009
Works very well, tnx
Sam on November 13, 2009
Works perfectly, thanks!
Yetkin Sakal on April 4, 2010
This is a life saver. Thanks!
Watanabex on April 5, 2010
Thanks for this, it helped a lot!!
Tim Sabat on June 16, 2010
This solved our issue with Highrise’s API. Thanks for the post.
Vivek Thomas on June 25, 2010
Thank you so much!!
I was sitting with this issue for a very very long time