On Fri, 17 Nov 2023 16:15:46 GMT, Darragh Clarke <[email protected]> wrote:
> Currently the descriptions of `URLEncoder.encode` and `URLDecoder.decode` > don't specify their use of replacement bytes or replacement character when > they cannot handle a character or sequence of bytes. This is longstanding > behavior but needs to be documented. > > **Solution** > - Added a new line to `URLEncoder.encode` API documentation to document that > the charset's replacement bytes are used. > > - Also changed `URLDecoder.decode` API documentation to document its use of > the charset's replacement character, also changed some wording. This pull request has now been integrated. Changeset: 48960df7 Author: Darragh Clarke <[email protected]> URL: https://git.openjdk.org/jdk/commit/48960df7bcb307a3b3353a1d513ddd4b3c0284ce Stats: 24 lines in 2 files changed: 11 ins; 7 del; 6 mod 8316734: URLEncoder should specify that replacement bytes will be used in case of coding error Reviewed-by: dfuchs, alanb ------------- PR: https://git.openjdk.org/jdk/pull/16709
