X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:reply-to:to:subject:from:content-type:content-transfer-encoding
	:message-id; q=dns; s=default; b=kJP1SeMSA1SSDdOXM424Oy2YkX7WWIT
	R02TLjC2B5fI6S3gC8Dk3Gy36vFCvCGXKij7M2sdf3r3EtjGwB0HLyun+DtQH+ra
	ZMqiGTBwWHVXfvTuvGnJFFLClcjlVQ6iT1kCNFmdUwgqoMYJ+xz9NLx9f2E1xtXl
	qgF1OIcB4mY0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:reply-to:to:subject:from:content-type:content-transfer-encoding
	:message-id; s=default; bh=Mj3Y0ZKdmFwUmxMldU/lMxlJo9o=; b=R7ULu
	wsRsk6jFGSnz3Zl0igDpA+nCQ2xiqY/HqAPAsIPHsT4I1zCS9eK3b1Uq1LGKsRfp
	Lc1km4NBCA6GPkH8JUFCYGYrOMLrDqK+6sMMQi4+pNoWX5QfXtphZ41qfxMdSSI5
	OZw1j64x1x/j2nnBk40TlKds/j0RnZxdaDCzzw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham version=3.3.1
MIME-Version: 1.0
In-Reply-To: <20130424125930.GQ26397@calimero.vinschen.de>
References: <51766C22.10702@bahnhof.se> <51770372.4070408@t-online.de> <20130424125930.GQ26397@calimero.vinschen.de>
Date: Wed, 24 Apr 2013 15:33:19 +0200
Reply-To: "Christian Franke" <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Difference in 32/64-bit curl.
From: "Christian Franke" <Christian.Franke@t-online.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <1UUzp1-23sI640@fwd56.aul.t-online.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:

src/tool_cfgable.h:89:
 bool include_headers;     /* ... */

src/tool_operate.c:886:
 my_setopt(curl, CURLOPT_HEADER, config->include_headers);

lib/url.c:704:
case CURLOPT_HEADER:
...
 data->set.include_header = (0 != va_arg(param, long))?TRUE:FALSE;


Christian




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

