----- Original Message -----
From: "Juraci Paixão Kröhling"
Sent: Friday, December 4, 2015 11:07:47 AM
Subject: Re: [Hawkular-dev] Fwd: [hawkular-ui-services] Slash hell: Preserving the
encoded slashes in the resource
On 04.12.2015 16:48, John Mazzitelli wrote:
> First, feeds don't care that these resource IDs might end up on URLs.
+1 . As a general comment not related to this particular
task/bug/whatever this is: places building URLs should *always* properly
encode/decode URL parts. Failing to do so is, among other things, a
Also part of the problem is that even if everything we write and control ourselves is
properly encoding the URL, it doesn't mean that this will properly work out on an
actual network somewhere.
There are other intermediary server which may control and route connections, and these
servers tend to really not like certain elements within a URL, even if they are properly
encode. We have already ran into a bunch of issues with this already where something else
doesn't like it and either blocks or mangles the URL before sending it off to our
Which sucks, because then our stuff wont work properly due to bugs in completely separate
So far we have come up work arounds (sort of, for one component it ended up that we just
couldn't use it), but I have a feeling eventually we may have to add an option to
base58 encode the metric id in the url