W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: Standard URL safe digest form and hash algorithm list

From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 29 Apr 2022 07:59:19 +0100
Message-ID: <CALGR9oaHCHgQms8xkT1BM5+hQ13_b+w0igBp6Sfo4LxoSM+9wQ@mail.gmail.com>
To: Roberto Polli <roberto@teamdigitale.governo.it>
Cc: Roman Volosatovs <roman@profian.com>, HTTP Working Group <ietf-http-wg@w3.org>, nathaniel@profian.com

On Fri, 29 Apr 2022, 07:44 Roberto Polli, <roberto@teamdigitale.governo.it>

> Hi Roman,
> Can you please file a github issue requesting the registration of two more
> digest algorithms?
> About the encoding, we decided to delegate it to SF. I don't remember why
> it was decided to use but instead of b64url though...
> Isn't decode/encode a viable solution?

I don't really see the issue here. The computed digest bytestring is the
same regardless of the serialization format for sending it over the wire.
The problem seems to be with trying to send the Structured Fields Byte
Sequence type in a URL. There's doesn't seem any need to do that, instead
you can just send the base64 encoding of the computed digest without the

Received on Friday, 29 April 2022 06:59:41 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:07 UTC