This is the mail archive of the
mailing list for the Cygwin project.
Re: Difference in 32/64-bit curl.
- From: "Christian Franke" <Christian dot Franke at t-online dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 24 Apr 2013 15:33:19 +0200
- Subject: Re: Difference in 32/64-bit curl.
- References: <51766C22 dot 10702 at bahnhof dot se> <51770372 dot 4070408 at t-online dot de> <20130424125930 dot GQ26397 at calimero dot vinschen dot de>
- Reply-to: "Christian Franke" <Christian dot Franke at t-online dot de>
Corinna Vinschen wrote:
> On Apr 23 23:56, Christian Franke wrote:
> > Fredrik Rothamel wrote:
> > >
> > >I just noticed that in 64-bit cygwin curl always include the
> > >http-headers in the response.
> > >(Old behaviour is to only include headers when -i option is
> > specified) >
> > >Is this an intentional change?
> > Unlikely. In this case it should be possible to revert the default
> > -i (--include) with --no-include.
> What about a type issue? int vs. long?
Yes, option is possibly set as int (bool) but retrieved as long:
bool include_headers; /* ... */
my_setopt(curl, CURLOPT_HEADER, config->include_headers);
data->set.include_header = (0 != va_arg(param, long))?TRUE:FALSE;
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple