afs commented on PR #2409: URL: https://github.com/apache/jena/pull/2409#issuecomment-2048534716
See [RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648) for the discussion and tables. There is also [RFC 2045](https://datatracker.ietf.org/doc/html/rfc2045) * [`xsd:base64Binary`](https://www.w3.org/TR/xmlschema-2/#base64Binary), which is defined to be RFC 2045 with the addition of XML white space making it RFC 4686 section 4. * Bearer tokens `enc64` uses RFC4648 table2 (RFC 4686 section 5) -- this may be wrong. The two areas of Base64 are different alphabets -- `XSDbase64Binary.java`, and `makeSkolem.java` is about `xsd:base64binary` which is RFC 2045 with white space and breaks at 76 characters. `AuthBearerTestLib.java` `enc64` uses is based around `base64url` (`encodeBase64URLSafeString`). OAuth and JWT seem to be `base64` (white space handling isn't clear). This is hidden because Apache Commons Codec Base64 decoding is universal. I am unclear what the right combination is. Performance links: * https://aws.amazon.com/blogs/developer/follow-up-on-base64-codec-performance * https://dkomanov.medium.com/base64-encoding-performance-jdk-vs-apache-commons-3fb83323414b -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
