Fix for specific characters in get params

[patotskiy]

If Request Url contains specific characters:

http://test.com/test-page/index.html?optradio=edge&config={%22uri%22:%22google.com22,%22width%22:640,%22height%22:360,%22test%22:{%22topPanel%22:true,%22autoPlay%22:true}}

than Har log request with incorrect Uri:

**http://test.comhttp://test.com**/test-page/index.html?optradio=edge&config={%22uri%22:%22google.com22,%22width%22:640,%22height%22:360,%22test%22:{%22topPanel%22:true,%22autoPlay%22:true}}

[jekh]

The host and port shouldn't be duplicated in HAR filter when the URI parsing fails. The best place to fix that is in HarCaptureFilter, where the duplication is occurring.

The curly braces {} shouldn't appear in a URL unescaped. RFC 1738 states:

Other characters are unsafe because
   gateways and other transport agents are known to sometimes modify
   such characters. These characters are "{", "}", "|", "\", "^", "~",
   "[", "]", and "`".
   All unsafe characters must always be encoded within a URL.

So, I'm not keen on changing our URI parsing from a standards-compliant parser to a non-standards-compliant parser. I do recognize that as a proxy BMP has to be pretty lenient, but I'd rather handle this by fixing the duplication issue in HarCaptureFilter when parsing an invalid URL (which the example URL certainly is).

[jekh]

This should be fixed in master now. Let me know if you still have issues with it.