Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119244
Message-ID: <09cd3838-6246-11b6-5201-33710bee70f2@gmx.de>
Date: Mon, 9 Jan 2023 19:55:36 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
To: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
References: <CAESVnVo3NyM_RGybyLQSko0F=fBSnSWG3gkVZtU-DS8W=79fdA@mail.gmail.com>
In-Reply-To: <CAESVnVo3NyM_RGybyLQSko0F=fBSnSWG3gkVZtU-DS8W=79fdA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:B5qviYeH7qc=;tPbD7o0zWu6jcz14mHwFnzqPtX/
 ggk3HKMo4pOK4MBh8+TZ4S6R8UPziU1f+RcQfEdqfyQ3GIitJwEadbNu4osb/6mQIhVSXCQ73
 4tEgGLEqkSQ0WI8wTDW+nECseTu2ukc69e+jWJmP0hqIYJhK6tPCws1iJl1PBDMi67HA6fdBB
 pNSuPiOhZ7iq0eUUC6RgDaDi7SavTteJXfaK8gTxyOk8sDQR5uyesAM9i5NZMicaMxgutIrSf
 gBnFxCeF5WUgX9pT4pTbG6fuMg1cb42h7DSGKooDt08xXTjIMCE7Mo+OD+4BmluxGwSqir3RJ
 KWMhcl7SspL2WDXMuleOiZpZw5C5VjJWeF41fBWzRsxxt/amdfrqD1By2P/90U401a1cY2s/m
 Yn/iROidjpz1oGt0I5ODIXgSKQurS4SPxTqc1KiAZg6+bbDxIEShQA6hYFgo1QZFfdW/PycJ3
 M76FKxo75ooAywCivwF6LOefWqxCZb1e/Nriaz0vo6j2LJdKwF4LUvxWnzNX3Mz2rPSinHmLe
 ASQ7DzKe6jfjenpYFGJ6MTDbqUxDt0fv3abytnOLxlyshRAxWf/PliKZSPCv/LXGm2KwTfOSb
 8I0WsrIBCYTrQtquscJ9cD04sT2beCsjuojNRL0WmHhBkDS5nQy1VNYKV3VGbcc24mt25H45f
 eJyFTA3aFWMS4zv6vDkdHsmBAUnAAFLBBDXKYpeehZeFGfzQeAoVjVkvOQB8K8GDyrncry3w2
 RxflSnqiDER6uPZimhRU1LZeoSvQ7gPVmyMJIVIJj4Hv112LGa+mAqlbnG5rUfHeM2aKU3EH1
 zuBtMSe4pf7CI7g/47KTtu0WWrKQxjZSgeFtXrfIu77y0724JRI9cCuwpkwqv3plB4VOsL2X2
 jjYVx7epI8k7vC47IRU7DvfdFtZzPUIISjTJFbRdW4aBj3eHM5/5hHUwYtmXE5UQvZj1nGDTS
 S2RqOA==
Subject: Re: base64url format
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 09.01.2023 at 19:49, Sara Golemon wrote:

> I've been working with JWTs lately and that means working with Base64URL
> format. (Ref: https://www.rfc-editor.org/rfc/rfc4648#section-5 )
> This is essentially the same thing as normal Base64, but instead of '+' =
and
> '/', it uses '-' and '_', respectively. It also allows leaving off the
> training '=3D' padding characters.
>
> So far, I've just been including polyfills like this:
>
> function base64url_decode(string $str): string {
>     return base64_decode(str_pad(strtr($str, '-_', '+/'), (4 -
> (strlen($str) % 4)) % 4, '=3D'));
> }
>
> function base64_encode(string $str): string {
>     return rtrim(strtr(base64_encode($str), '+/', '-_'), '=3D');
> }
>
> These work fine, but they create a LOT of string copies along the way wh=
ich
> shouldn't be necessary.
> Would anyone mind if skipped RFC and just added `base64url_encode()` and
> `base64url_decode()` to PHP 8.3?
>
> Can hold a vote if anyone objects, but this seems fairly non-controversi=
al.

IMO, go with a PR first.  If that is controversial, an RFC can still be
done.

I, personally, would be more interested in base32, but that's another stor=
y.

=2D-
Christoph M. Becker