From nobody Tue Mar 1 13:25:14 2022 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 60C9819EB168 for ; Tue, 1 Mar 2022 13:25:34 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from mail.ish.com.au (203-129-16-229.cb8110.syd.nbn.aussiebb.net [203.129.16.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4K7J0D5kHjz4nF7 for ; Tue, 1 Mar 2022 13:25:32 +0000 (UTC) (envelope-from ari@ish.com.au) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ish.com.au; s=mail; h=In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID :Content-Type:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=wir08BPi8BvxD4fYSj1WN+28jFt88jFxji2F3v7Nizw=; b=azTq2/hJ2N29anOqHf5jBi4HdI SMDz96qz8/kR2dCvzNbv+jh1pI685DioxbhkqUOCiH6pSCMEO/TZ/+oCLqy7IN8z8l6LG6XPIxb9U X6G6BpRbA9mIFPialtGitjm4FZ3Fr4q8vf2i6OLZ4z2NxPCWtYZs2gIe+6joOi4MJgP4ZhVDfFvll OHSNxDpvEEoxrxvs1XCUbFVECQf5DahY5WJSK6iUboc3B3sKtTa18q1Y7iGE4A4N4ZsmzsTyhe6la jLhiUcB7Lb3jZ6Uznfnntsv+AgCwU0rs4ecD4uEoZeQi9EccWNNG+kRtzAxIf402bp8dQ+jP3+AAx duaQ0gLQ==; Received: from 159-196-105-163.9fc469.syd.nbn.aussiebb.net ([159.196.105.163] helo=[10.29.62.214]) by mail.ish.com.au with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1nP2Uc-000Fbq-9o; Wed, 02 Mar 2022 00:25:15 +1100 Content-Type: multipart/alternative; boundary="------------azIZFDKkTE0WVMe0L0lPl8U0" Message-ID: <378a27ca-dbfe-d6f4-45f6-2ff90265874e@ish.com.au> Date: Wed, 2 Mar 2022 00:25:14 +1100 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: pkgs contain non URL safe characters Content-Language: en-US To: Ronald Klop , freebsd-ports@FreeBSD.org References: From: Aristedes Maniatis In-Reply-To: X-Rspamd-Queue-Id: 4K7J0D5kHjz4nF7 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ish.com.au header.s=mail header.b="azTq2/hJ"; dmarc=pass (policy=quarantine) header.from=ish.com.au; spf=pass (mx1.freebsd.org: domain of ari@ish.com.au designates 203.129.16.229 as permitted sender) smtp.mailfrom=ari@ish.com.au X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[ish.com.au:s=mail]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ish.com.au:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[ish.com.au,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-ports]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:4764, ipnet:203.129.16.0/22, country:AU]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------azIZFDKkTE0WVMe0L0lPl8U0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 1/3/2022 10:57pm, Ronald Klop wrote: > > The + character is not special in this part of the URL. The request > send by pkg is compliant to the specs. > > I'm aware of having specs and having what browsers and servers do in > real life. > Why does Cloudfront decode a + to a space in this part of the URL? > > Regards, > Ronald. You are exactly correct. Turns out that AWS S3 is not following RFC 1866 and hasn't since the beginning. And I'm guessing it is now too late. With this new information I've finally found a thread complaining about this (it affects other repos like apt). https://forums.aws.amazon.com/thread.jspa?threadID=55746 My little hack of renaming openjdk packages will have to stay I guess. Thanks Ari --------------azIZFDKkTE0WVMe0L0lPl8U0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

On 1/3/2022 10:57pm, Ronald Klop wrote:


The + character is not special in this part of the URL. The request send by pkg is compliant to the specs.

I'm aware of having specs and having what browsers and servers do in real life.
Why does Cloudfront decode a + to a space in this part of the URL?

Regards,
Ronald.


You are exactly correct. Turns out that AWS S3 is not following RFC 1866 and hasn't since the beginning. And I'm guessing it is now too late. With this new information I've finally found a thread complaining about this (it affects other repos like apt).

https://forums.aws.amazon.com/thread.jspa?threadID=55746


My little hack of renaming openjdk packages will have to stay I guess.


Thanks

Ari

--------------azIZFDKkTE0WVMe0L0lPl8U0--