By "practical" I mean that this possibility will be obvious from the curl manual and not only from the code and the sniffer.

------------------------------------------------------------------------------------
-- A false sense of security is worse than a true sense of insecurity.

-----Original Message-----
From: Daniel Stenberg [mailto:daniel-curl_at_haxx.se]
Sent: Monday, August 23, 2004 4:04 PM
To: libcurl development
Subject: RE: Expect:100 continue

On Mon, 23 Aug 2004, Roman Koifman wrote:

> I think there should be a possibility to turn this mechanism off even for
> HTTP 1.1. (To support HTTP 1.1 servers and proxies without 100-mechanism
> support). Indeed it is possible to turn it off using the empty "Expect:"
> header , but IMHO it will be more practical to turn it off using the
> curl_setopt.

I'm not so sure we need an extra way of doing it. We still need to allow users
to disable it by providing an empty one, as that is the universal
disable-headers approach in libcurl.

"more practical" you say. You mean it makes your code two or three lines
smaller? Or are there any other practical reasons?

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html
*****************************
Finjan Software
This e-mail and any attached files are confidential and may be legally
privileged. The unauthorized use, disclosure or copying of this email or
any information contained within it is strictly prohibited. This also
confirms that Finjan Software's Vital Security for E-Mail has scanned this
message for the presence of known viruses and potentially malicious
code.
Finjan Software - Prevention is the Best Cure!
*****************************