encoding/json: marshaller does not provide Base64Url support #14804
Milestone
Comments
What's wrong with doing it client side instead of making the json encoder do mime sniffing on the data?
|
@OneOfOne There's nothing wrong with sniffing in a browser scenario but I'm targeting another class of applications where there is no room for such measures: https://cyberphone.github.io/openkeystore/resources/docs/jsonsignatures.html Yes, an option must also work for unmarshalling. |
It's rather trivial to implement your own type for that though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://play.golang.org/p/k1Wgec8cVB
I had hoped that there would be a field option allowing you to override the default encoding because Base64Url is nowadays the preferred format in standards including IETF's JOSE
No such option :-)
The text was updated successfully, but these errors were encountered: