going back to using the uri parsing library

regexes that i've used fail in edge cases (like a variable containing an html encoded entity that starts with an & or are too greedy and eliminate good parameters in the middle of the parameter string