Solution for live search double encoding URLs

Remco Bakx December 9, 2021

When using the live search, the URLs of the results are double encoded, e.g. when a  contains a '&', this is encoded as %2526 instead of %26. As a result, the user get a 404 page instead of the the file being downloaded.

Several issues have been reported in the past about the live search double encoding filenames, like e.g. this one: CONFSERVER-32869 

Although this issue is reported as resolved, in our instance which runs version 7.14.1, we still encounter this issue. 

Does anybody experience the same issue or have a solution for this?

1 answer

0 votes
Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 15, 2022

Hi @Remco Bakx 

Preferably there is a recommendation not to use special characters in Page title, in spite of that reporting issues is no big concern I would say. Ain't it?

Being said that, if you are searching for content with special characters, I would suggest not using them at all

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.14.1
TAGS
AUG Leaders

Atlassian Community Events