registry function _fUrlInit(), parsing '&' in bad furl

[Wolfie]

Was wondering if there's a reason that bad FURL's with & in them are exempt from being flagged as a bad URL and if there's a way to set it as an optional thing in future versions without having to edit the register file.