-
Type:
Bug
-
Status: Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: 3.2.0
-
Fix Version/s: 4.0.0
-
Component/s: None
-
Labels:None
-
Similar issues:
-
Processed by team:Pulsar
-
Sprint:Platform Sprint 132
If you (mis)use <hst:link> tag with absolute URL path attribute, it removes the scheme part only.
For example,
<hst:link path="https://www.example.com/index.html" />
renders /www.example.com/index.html (note only 'https:/' part removed) since 10.
It used to return the path attribute value without changing any before until 7.9
-----------
I think this is kind of regression by HSTTWO-3423. I saw this commit related to this:
commit 0b2161228e85935390605012eee9242380ac007f HSTTWO-3423 When the pathInfo is used from the HstLinkTag, then while the pathInfo starts with http:, https: or // , the pathInfo should strip off those prefixes: We do not allow those.
But I think it should have returned the original path value without having to strip any forbidden prefixes (e.g, https: ), giving a warning optionally, without breaking any old behavior until 7.9.
- is a result of
-
HSTTWO-3423 Align path info encoding with rest of URL encoding
-
- Closed
-
- is cloned by
-
HSTTWO-3702 [Backport 3.2] HST Link Tag removes scheme when path is set to http(s)://...
-
- Closed
-
-
HSTTWO-3703 [Backport 3.1] HST Link Tag removes scheme when path is set to http(s)://...
-
- Closed
-
-
HSTTWO-3704 [Backport 7.9] HST Link Tag removes scheme when path is set to http(s)://...
-
- Closed
-
-
HSTTWO-3705 [Backport 7.8] HST Link Tag removes scheme when path is set to http(s)://...
-
- Closed
-