Hi Joe,
What happens when someone logs a bug for system IDs containing IPv6 addresses
and non-percent encoded international characters?
On Jul 10, 2012, at 3:42 AM, Joe Wang wrote:
Hi Paul,
I'm back from vacation.
You're right. But such an error is also expected. The original design
On 7/9/2012 10:59 PM, Paul Sandoz wrote:
Hi Joe,
What happens when someone logs a bug for system IDs containing IPv6 addresses
and non-percent encoded international characters?
Exception would be expected just as if Xerces is used.
On Jul 10, 2012, at 3:42 AM, Joe Wang wrote:
Hi Paul,
Hi Joe,
If you are gonna fix things to support IPv6 addresses in URLs i really think
you need to make it work for URLs with international characters too.
On Jul 10, 2012, at 8:50 PM, Joe Wang wrote:
602 if (reader == null) {
603 stream = xmlInputSource.getByteStream();
Hi Paul,
I agree, it looked quite messy, isn't it :), keeping a hack that
generates encoded url and yet not support IPv6 addresses that contain
international characters?
It IS a more preferable solution to remove the hack of using
escapeNonUSAscii -- so I'll do :)
Thanks,
Joe
On
Hi Paul,
I'm back from vacation.
You're right. But such an error is also expected. The original design
never tried to out-do the java.net.URL. If a system ID input fails URL,
it shall result in an exception.
The patch that supplied the extra encoding was provided to both Sun and
Apache,
