From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH] Add MARS shooter. Date: Sun, 20 Sep 2015 09:51:55 +0200 Message-ID: <87oagx5y04.fsf@elephly.net> References: <8761377ct3.fsf@elephly.net> <871tdu7r3f.fsf@elephly.net> <87twqq5g3o.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdZPs-0008W6-D2 for guix-devel@gnu.org; Sun, 20 Sep 2015 03:52:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZdZPn-0000JX-VZ for guix-devel@gnu.org; Sun, 20 Sep 2015 03:52:08 -0400 Received: from sender163-mail.zoho.com ([74.201.84.163]:25339) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdZPn-0000JL-NQ for guix-devel@gnu.org; Sun, 20 Sep 2015 03:52:03 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: "Thompson, David" Cc: guix-devel >>> No, upstream needs to fix their invalid Content-Type header. We've >>> had this problem a few times, most recently with rubygems.org, and in >>> all cases we've gotten upstream to fix it. Strict header parsing can >>> seem like an issue at times, but it's really a very good feature that >>> the rest of the world seems to ignore. [0] >> >> I wonder what a correct Content-Type header would look like in this >> case. I would like to submit a helpful report containing what I got and >> what it should have been. > > In this case, application/x-gzip or application/octet-stream would be > appropriate. Less specifically, the media type needs to match the > syntax as defined by the W3C spec. [0] Thanks, I opened a support ticket with Github.com. ~~ Ricardo