Re: base64 URL decode - for jwt -- MIDRANGE-L

Subject: Re: base64 URL decode - for jwt
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Mon, 10 Mar 2025 21:20:04 -0500
Auth-sender: vhamberg@xxxxxxxxxxxxxxx
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hi Chris

As I understand it, and I think Jay mentioned it, the so-called BASE4 part is actually BASE64URL - this replaces a couple things in BASE64 that don't work in URLs - like a forward slash, I believe. I forget, but I looked it up.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.