Since there are 2 new functions, should'nt the SONAME be bumped ?
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
On 20 July 2015 at 14:10, Patrick Monnerat
patrick.monne...@datasphere.ch wrote:
Since there are 2 new functions, should'nt the SONAME be bumped ?
No. Programs using an old libcurl version will continue working with
the latest version... so the soname stays the same.
If libcurl would use symbol
Cristian Morales Vega wrote:
Since there are 2 new functions, should'nt the SONAME be bumped ?
No. Programs using an old libcurl version will continue working with
the latest version... so the soname stays the same.
If libcurl would use symbol versioning the way glibc does,
curl_multi_setopt
Hi,
Currently, libcurl rejects responses with Content-Encoding: compress
when CURLOPT_ACCEPT_ENCODING is set to . I think that libcurl should
treat the Content-Encoding compress the same as other
Content-Encodings that it does not support, e.g. bzip2. I have
attached a patch for this.
Kamil Dudka wrote:
This won't change the final SONAME on platforms which support what
you
described, because they use C-A for SONAME. But others (i.e.:
iSeries)
will bump (they use C alone).
What is the actual motivation to do so?
If applications and other libraries are built against the
On Monday 20 July 2015 16:44:48 Patrick Monnerat wrote:
Cristian Morales Vega wrote:
Since there are 2 new functions, should'nt the SONAME be bumped ?
No. Programs using an old libcurl version will continue working with
the latest version... so the soname stays the same.
If libcurl
On 7/17/2015 2:40 PM, Fitzgerald, Kevin wrote:
Thank you for the example. But I think I am not going about this correctly.
What I actually need to be able to do is connect to a web service (which it
appears I am able to do), and send it a POST request. Below is an example of
the request that I
Fitzgerald, Kevin wrote:
curl -u user:pass --data-binary @soapreq.xml -H Content-Type:
text/xml; charset=utf-8 -H SOAPAction:
\https://workweb.dwd.state.wi.us/KIDS/LicenseCertification/Service/chec
kCertifications\
https://workweb.dwd.state.wi.us/KIDS/LicenseCertification/Service/check
Hello,
Yes, I do realize that the URL cannot contain a line feed character (hence the
error I’m having). I’ve already made changes to read the file without the LF
character, but I wanted to ask here (actually on the curlpp mailing list) for
an option to ignore this character.
Anyway, I’ve fixed
On Mon, 20 Jul 2015, Tiago Cerqueira (1090678) wrote:
Yes, I do realize that the URL cannot contain a line feed character (hence
the error I’m having). I’ve already made changes to read the file without
the LF character, but I wanted to ask here (actually on the curlpp mailing
list) for an
On Jul 20, 2015, at 9:57 AM, Patrick Monnerat
patrick.monne...@datasphere.ch wrote:
Fitzgerald, Kevin wrote:
Thanks for this, but it looks like a command line request. What I need
to do is send my POST within a C program in a UNIX environment.
If you add --libcurl skeleton.c to a curl
11 matches
Mail list logo
