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
	:content-type:content-transfer-encoding; q=dns; s=default; b=Sey
	XMsKkwC27ZLoOir0cMl4zKy7VI7wLy5e8Y+TJGp2E7zXJhItcZcNkUW1VuqfLaF7
	pBDqWu+XSzi68EMBhAiPNuCqa/QTlHTeCi4WdBF6U4hToVt4k+YXhlbjJOk/Q5Rl
	cmVgR+3NTLYrKkOm+NbNfpiIE+vaYgNxVLuxJmV4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51766C22.10702@bahnhof.se>
Date: Tue, 23 Apr 2013 13:10:26 +0200
From: Fredrik Rothamel <fredrik.rothamel@bahnhof.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Difference in 32/64-bit curl.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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?
Makes some scripts misbehave...

BTW: Big thanks to the cygwin team for the 64-bit porting effort. Any 
way I can help?

Regards,
Fredrik

--
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