X-Recipient: archive-cygwin AT delorie DOT 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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Xfr6+lYR2yuo6VpCFQQCb80/cNHgT82C58/sUPKNGWJ
	bDK7x8rqh48ZLKj9V6OLwKWF3439OHCjlm4eZEeZm1jFv/BdQEnCmqUClqWVN+RE
	2dBhRJ5HVnoaaeP3PbumipFOwhI/0k+JeLUo849DGhQ7RiJEWjQVtZfm2N747kIg
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=Vqh0U9pYL6D5mwAM/S26ZrEUVaA=; b=AphFpHZZj7PMLM/MG
	UEh9+nYChXwE5nCMjCjQV6AesuTd0XjxtQw3Cj1RHTrVb4zxk5mAuJYz4yRsiOfk
	SluLAv8AmxU/c3ZGycZ64BbN76MKOhAt8LE3Jm0PUAInIoQKKvgXiJ+HfWbyfP0E
	PZyHSvfuO6RrhQAjPKSFufhEgs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_20,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SEMBACKSCATTER,RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham version=3.3.1
Message-ID: <51770372.4070408@t-online.de>
Date: Tue, 23 Apr 2013 23:56:02 +0200
From: Christian Franke <Christian DOT Franke AT t-online DOT de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 SeaMonkey/2.16.2
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Difference in 32/64-bit curl.
References: <51766C22 DOT 10702 AT bahnhof DOT se>
In-Reply-To: <51766C22.10702@bahnhof.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Fredrik Rothamel wrote:
> Hi,
>
> 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.

According to a quick gdb session using curl-debug package the 
corresponding variable config->include_headers is not set during option 
processing. But later in Curl_setopt(., CURLOPT_HEADER, .) the variable 
data->set.include_header is set true because some va_arg(param, long) is 
nonzero.

Possibly a __builtin_va_list related gcc bug.

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