Re: encode/decode support for base64url
| От | Florents Tselai |
|---|---|
| Тема | Re: encode/decode support for base64url |
| Дата | |
| Msg-id | 2A234F6B-E7F8-443B-A2D6-FF31C4A29D9C@gmail.com обсуждение исходный текст |
| Ответ на | Re: encode/decode support for base64url (Aleksander Alekseev <aleksander@timescale.com>) |
| Ответы |
Re: encode/decode support for base64url
|
| Список | pgsql-hackers |
On 7 Mar 2025, at 4:40 PM, Aleksander Alekseev <aleksander@timescale.com> wrote:Hi,Sometimes support for base64url from RFC 4648 would be useful.
Does anyone else need a patch like this?
While not a frequent ask, it has been mentioned in the past. I think it would
make sense to add so please do submit a patch for it for consideration.
IMO it would be nice to have.
Would you like to submit such a patch or are you merely suggesting an
idea for others to implement?
--
Best regards,
Aleksander Alekseev
Just to confirm:
CREATE FUNCTION base64url_encode(input bytea) RETURNS text AS $$
SELECT regexp_replace(
replace(replace(encode(input, 'base64'), '+', '-'), '/', '_'),
'=+$', '', 'g'
);
$$ LANGUAGE sql IMMUTABLE;
CREATE FUNCTION base64url_decode(input text) RETURNS bytea AS $$
SELECT decode(
rpad(replace(replace(input, '-', '+'), '_', '/'), (length(input) + 3) & ~3, '='),
'base64'
);
$$ LANGUAGE sql IMMUTABLE;
With minimal testing, this yields the same results with https://base64.guru/standards/base64url/encode
select base64url_encode('post+gres')
base64url_encode
------------------
cG9zdCtncmVz
(1 row)
В списке pgsql-hackers по дате отправления: