> I think it is useful to explore how generic these real-world URI > parsers really are. I just tried to use > > http://%3134.169.34.18/ and http://134.169.34.%31%38/ > > to access a web page, expecting that parsers would turn that into > > http://134.169.34.18/ > > but I got lots of "host not found" messages.
My web browser behaves as the same for these examples. But it is terminated by inputing the following illegal notations. http://134.169.34.1%8/ http://134.169.34%.18/ http://134.169.3%4.18/ http://134.169.34.18%en0/ OTOH, it is not terminated by the following notations. http://[::1%4]/ http://[::1%en0]/ Hence, illegal '%' notation may not be safe for some implementation. But illegal '%' notation in [::] might be treated specially. Regards, Noritoshi Demizu -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
