Scala Common Enrich: bump scala-uri to 0.5.0

[christoph-buente]

We see decent amount of requests ending up in the bad bucket, because of page_url contains more than one # character. Like this one:

Provided URI string [http://www.example.com/path/index.ssf/2016/09/taco_charlton_jourdan_lewis_tr.html#incart_river_index#incart_m-rpt-2] could not be parsed by Netaporter: [Illegal character in fragment at index 104: http://www.example.com/path/index.ssf/2016/09/taco_charlton_jourdan_lewis_tr.html#incart_river_index#incart_m-rpt-2]

Essentially all browsers i tried could handle that URL, even though regarding to the spec it might not be valid. Is there a way to let those type of event through?

[christoph-buente]

Are we the only ones seeing this behaviour? @alexanderdean?

[alexanderdean]

The Netaporter library we use is the most permissive URI parser available for the JVM - it would be worth raising an issue there and seeing if they are up for tolerating URIs with 2 fragments attached? If not, we're really back looking at #351...

[christoph-buente]

Thx @alexanderdean,

and you know what, there is an issue already, regarding double fragment separators:
https://github.com/NET-A-PORTER/scala-uri/issues/114

I left a comment and asked for the changes.

[alexanderdean]

Cool, sounds like a plan @christoph-buente !

[christoph-buente]

@alexanderdean: I've never seen a faster fix!
https://github.com/NET-A-PORTER/scala-uri/commit/22dd7672c9c3af68facbf949069fbfa4e67df468

[alexanderdean]

Wow! Thanks so much @theon.

[theon]

No problem!

[christoph-buente]

@alexanderdean Has this dependency bump released ever since?

[alexanderdean]

Not yet!