Fixing error due to misuse of url.parse(..)

This is blocking data-load on the QA environment.

There are cases where we feed the result of `url.parse(reqUrl)` back into `url.parse`. node 0.8.23 would gracefully handle this depending if the first parameter was a object or string. node 0.8.24 does not gracefully handle this and instead throws an Error.

This fix ensures we always pass the reqUrl string as the first parameter, not the parsed object.