less string URL parsing...

[Thiago Macieira]

Thiago Macieira wrote:
>Another solution, which wouldn't involve using maybe-not-allowed domain
>names, is to use a top-level domain name:
>
>http://www.yahoo.com.cache.
>
>(The extra ending dot is not necessary and currently makes no
> difference. See bug #93008)
>
>In all, I think your way out is to use a name that doesn't exist and
> will never exist, instead of using names that are not allowed to exist.

Another idea: use one of the freed work-in-progress ACE prefixes:

   The ACE prefix, used in the conversion operations (section 4), is two
   alphanumeric ASCII characters followed by two hyphen-minuses.  It
   cannot be any of the prefixes already used in earlier documents,
   which includes the following: "bl--", "bq--", "dq--", "lq--", "mq--",
   "ra--", "wq--" and "zq--".

or "xx--":

I.e.: http://xx--cache.www.yahoo.com
or: http://www.yahoo.com.xx--cache

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiago (AT) macieira (DOT) info
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20041203/bd6ad7d1/attachment.sig>