fixes issue #367

By escaping '+' chars before call to url.QueryUnescape
This check isn't necessary — strings.Replace is already optimized to do nothing if the substring isn't found. This just makes the code a little slower in the case where a "+" is found. So you can reduce the function to just the strings.Replace call; but then it's not really worth having a function for it, so you can just put the strings.Replace call into the PathVar function :)