On Thu, 18 Dec 2003, Jacob Swed wrote:

> Not exactly. The problem is clearly that you don't know in what, if any,
> authentication will be required in advance. The "fake" GET is clearly a
> problem waiting to happen since the METHOD is still PUT, SEARCH, PROPFIND or
> whatever. The problem is that curl really needs to be doing a true PUT (or
> whatever) but with just the headers. It should then send the body only if it
> receives an HTTP 100 Continue response.

You are of course right. Your described approach is exactly what needs to be
done.

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click