If you're testing your app locally, use Charles to examine the data: http://www.charlesproxy.com/
-- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Tue, Dec 23, 2008 at 9:02 PM, Stecki <[email protected]> wrote: > >> > I still haven't seen a Charles trace on what the client is actually >> > sending. >> > If the client is indeed sending a bogus Expect: header, then all this line >> > is >> > doing is suppressing it. > > I for my part had never explicitly set an Expect: header. Seems that > Curl is doing this automagically. But until tonight it never was a > problem - so the new apache may indeed be a bit more picky, what to > accept. > > My code was: > > curl_setopt($ch, CURLOPT_HTTPAUTH,CURLAUTH_BASIC); > curl_setopt($ch, CURLOPT_USERPWD,"user:pass"); > curl_setopt($ch, CURLOPT_URL, $url."?status=".urlencode($t)); > curl_setopt($ch, CURLOPT_POST,true); > curl_setopt($ch, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_1); > curl_setopt($ch, CURLOPT_HEADER, false); > curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); > > and I just added > > curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); > > to get it to work. > > Sorry, I don't know how to get the verbose trace info. > > >
