On 17 Jan 2013, at 12:35, Chrysovaladis Datsios wrote: > Hi, > this is a patch for the feature request as described in > http://sourceforge.net/p/curl/feature-requests/67/ > the feature is a standard in > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.40
I welcome this improvement but I agree with Dan Fandrich that it would be more useful if implemented as a callback. My use cases for request trailers involve signing operations on the message body where it's expensive to buffer the whole request before starting to send the body… especially as parsing the trailer would be optional. > Example case: Chunked PUT request with Trailer headers. > > PUT /myfile HTTP/1.1 > Host: 10.8.60.209 > Accept: / > Transfer-Encoding: chunked > Trailer: mytrailerheader > Expect: 100-continue > > 53 > ....first chunk of data...... > > > 53 > .....second chunk of data..... > > > 0 > mytrailerheader: myvalue Why is the client sending Expect: 100-continue here? As an aside, the Accept: header also looks invalid. -- Tim Bannister – is...@jellybaby.net
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
