On Fri, 29 Nov 2002, Sara Golemon wrote: > I'm not so much worried about the user in this case, a few explodes will > keep them happy. I'm more worried about the behavior of parse_url being > just plain lacking. mailto:[EMAIL PROTECTED]?subject=Bug+20308 should be > entitled to everybit as much parsing as > http://joe:[EMAIL PROTECTED]/pathto/somepage?var=value > > The ONLY real concern here, and reason for not fixing php_url_parse, comes > in the fact that 'path' would no longer contain > '[EMAIL PROTECTED]?subject=Bug+20308' (per the example above) which would > likely break existing scripts.
Because mailto URL is not one of the common internet/host URLs (that parse_url was designed to handle), this should not happen. > Perhaps the compromise is to create a new function 'parse_url_rfc' (name > could be better) which behaves correctly (without having special cases). > Then add a note to the manpage for parse_url saying to use parse_url_rfc > instead, and eventually depricate parse_url (perhaps with PHP 5.0). But which RFC would it follow? There are at least 3 :) Why not just use the Net_URL pear package? --Wez. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
