On 29 Mar 2005, Daniel Stenberg wrote:
> On Mon, 28 Mar 2005, Augustus Saunders wrote:
> >>Then in what way doesn't FAILONERROR do what you want? And if not, isn't
> >>returning an error from a header callback good enough to add a "custom"
> >>abort?
> >
> >I can't quite tell what FAILONERROR is doing. What I want is for the
> >upload to abort if an error is returned. Especially since an "error" will
> >often be 407--I can't make my users wait for 3 minutes of uploading only
> >to pop up a proxy auth dialog and then try again! No point in
> >transmitting 50 megabytes if the server ain't taking it. And yes, I can
> >do some magic in the header callback, but this seems so obvious I kind of
> >assumed there was already an option for it.
>
> This is where "Expect: 100-continue" should be used I guess. libcurl
> doesn't add that by default for plain posts. Otherwise there's no way for
> the server to signal error until you've sent the whole post...

Do you really mean that libcurl doesn't send "Expect: 100-continue"
for posts? A server certainly _can_ signal an error without waiting
for the whole post, whether you send "Expect: 100-continue" or not.

-- Jamie
Received on 2005-04-26