You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In handling byte[] <--> String conversion, there are many places where
ESAPI is simply defaulting to use native byte encoding. Unfortunately, as
different OS platforms have different encoding mechanisms this hinders
portability across platforms.
This issue is to make all such conversions consist to use UTF-8 encoding.
Without this unexpected problems can arise, especially when in dealing with
encryption or serialized Java objects.
From kevin.w.wall@gmail.com on November 06, 2009 18:01:18
In handling byte[] <--> String conversion, there are many places where
ESAPI is simply defaulting to use native byte encoding. Unfortunately, as
different OS platforms have different encoding mechanisms this hinders
portability across platforms.
This issue is to make all such conversions consist to use UTF-8 encoding.
Without this unexpected problems can arise, especially when in dealing with
encryption or serialized Java objects.
Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=51
The text was updated successfully, but these errors were encountered: