Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 2 Mar 2022 00:25:14 +1100
From:      Aristedes Maniatis <ari@ish.com.au>
To:        Ronald Klop <ronald-lists@klop.ws>, freebsd-ports@FreeBSD.org
Subject:   Re: pkgs contain non URL safe characters
Message-ID:  <378a27ca-dbfe-d6f4-45f6-2ff90265874e@ish.com.au>
In-Reply-To: <e4f364c7-a2ef-7b03-77af-2d8dd8299b80@klop.ws>
References:  <e4f8bec4-e2c7-154c-0e49-109718782725@ish.com.au> <e0aea756-b7c3-b9bf-9dc7-b34c91399b31@ish.com.au> <e4f364c7-a2ef-7b03-77af-2d8dd8299b80@klop.ws>
next in thread | previous in thread | raw e-mail | index | archive | help 
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 
<https://datatracker.ietf.org/doc/html/rfc1866>; 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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>On 1/3/2022 10:57pm, Ronald Klop wrote:<br>
    </p>
    <blockquote type="cite"
      cite="mid:e4f364c7-a2ef-7b03-77af-2d8dd8299b80@klop.ws"><br>
      The + character is not special in this part of the URL. The
      request send by pkg is compliant to the specs.
      <br>
      <br>
      I'm aware of having specs and having what browsers and servers do
      in real life.
      <br>
      Why does Cloudfront decode a + to a space in this part of the URL?
      <br>
      <br>
      Regards,
      <br>
      Ronald.
      <br>
    </blockquote>
    <p><br>
    </p>
    <p>You are exactly correct. Turns out that AWS S3 is not following <a
        href="https://datatracker.ietf.org/doc/html/rfc1866"
        rel="nofollow noreferrer">RFC 1866</a> 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).</p>
    <p><a class="moz-txt-link-freetext" href="https://forums.aws.amazon.com/thread.jspa?threadID=55746">https://forums.aws.amazon.com/thread.jspa?threadID=55746</a></p>;
    <p><br>
    </p>
    <p>My little hack of renaming openjdk packages will have to stay I
      guess.</p>
    <p><br>
    </p>
    <p>Thanks</p>
    <p>Ari<br>
    </p>
  </body>
</html>

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

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?378a27ca-dbfe-d6f4-45f6-2ff90265874e>