Open adulbrich opened 2 years ago
@MFSY are you comfortable with the acceptance criteria above? do you want to keep backward compatibility?
@MFSY any feedback on this?
@dhaneshnm come up with list of examples to show impact for DKE (notify them once we have it)
Hi,
Find below a description of this issue from my perspective. First of all, this is a bug to fix and not a feature request from my side.
Currently when display resources in some plugins, an already url encoded _self
value is url encoded again leading to a double url encoding. The value of the resource _self
property:
With this in mind, it would important to detect on the plugins side when it is already url encoded so that double url encoding is not happening.
Best.
As reported by @MFSY:
Currently, I have to write (this might cause issues on clients) [as value to
distribution.contentURL
e.g.]:Instead of (which is the best/preferred way of having HTTP URLs as paths in a URL):
Affected (or to check) plugins:
Acceptance Criteria:
contentURL
s in the correct form, where the URL is encoded (e.g.https://bbp.epfl.ch/nexus/v1/files/bbp/lnmce/https%3A%2F%2Fbbp.epfl.ch%2Fneurosciencegraph%2Fdata%2Ffd68fe86-2424-42df-b4e4-d110d59bc805
)contentURL
is encoded, nothing should happencontentURL
does not match the right format (e.g.https://bbp.epfl.ch/nexus/v1/files/bbp/lnmce/https://bbp.epfl.ch/neurosciencegraph/data/fd68fe86-2424-42df-b4e4-d110d59bc805
)Not in scope:
contentURL
is not encoded, we should encode it