You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When tracking a download/outlink URL it keeps the full URL including protocol but also sets an url_prefix. It should only do one of them but not both. It shouldn't set the url prefix when it keeps the http(s) protocol, or maybe it should remove the http in the action when it sets a url prefix...
This might be a more proper fix but not sure if it would regress anything
For BC I'm not sure if it be better to no longer set url_prefix or to no longer store the protocol. Likely it be easier to not store the url_prefix anymore and set it to null instead since it should make aggregating the data easier.
The text was updated successfully, but these errors were encountered:
tsteur
added
the
Bug
For errors / faults / flaws / inconsistencies etc.
label
Dec 8, 2019
tsteur
added
worksforme
The issue cannot be reproduced and things work as intended.
and removed
Bug
For errors / faults / flaws / inconsistencies etc.
labels
Dec 23, 2019
refs #15233
When tracking a download/outlink URL it keeps the full URL including protocol but also sets an url_prefix. It should only do one of them but not both. It shouldn't set the url prefix when it keeps the http(s) protocol, or maybe it should remove the http in the action when it sets a url prefix...
This might be a more proper fix but not sure if it would regress anything
For BC I'm not sure if it be better to no longer set url_prefix or to no longer store the protocol. Likely it be easier to not store the url_prefix anymore and set it to
null
instead since it should make aggregating the data easier.The text was updated successfully, but these errors were encountered: