commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CODEC-145) Base64.encodeBase64String could better use newStringUsAscii
Date Tue, 28 Mar 2017 15:05:41 GMT

     [ https://issues.apache.org/jira/browse/CODEC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb resolved CODEC-145.
------------------------
       Resolution: Fixed
    Fix Version/s: 1.11

URL: http://svn.apache.org/viewvc?rev=1789158&view=rev
Log:
CODEC-145 Base64.encodeBase64String could better use newStringUsAscii (ditto encodeBase64URLSafeString)

Modified:
    commons/proper/codec/trunk/src/changes/changes.xml
    commons/proper/codec/trunk/src/main/java/org/apache/commons/codec/binary/Base64.java



> Base64.encodeBase64String could better use newStringUsAscii
> -----------------------------------------------------------
>
>                 Key: CODEC-145
>                 URL: https://issues.apache.org/jira/browse/CODEC-145
>             Project: Commons Codec
>          Issue Type: Bug
>            Reporter: Jesse Glick
>            Priority: Minor
>              Labels: base64
>             Fix For: 1.11
>
>
> {{org.apache.commons.codec.binary.Base64.encodeBase64String}} currently uses {{StringUtils.newStringUtf8}}.
But the text should be in fact be in ASCII, so {{newStringUsAscii}} would be clearer and perhaps
faster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message