Cyrillic URLs encoding issue when configured by Vanity URL Redirect

[Neehakethi]

Parent Issue

No response

Problem Statement

Cyrillic URL encoding issue, when configured by Vanity URL Redirect to an external Page.

When trying to pass Cyrcllic URL and configuring a vanity URL , The decoded characters are being passed wrongly to the external site

Steps to Reproduce

1. Create a vanity URL on the demo site (Screenshot attached)
   
2. Try accessing https://demo.dotcms.com/test/%D0%BC%D0%B5%D1%82%D0%B0%D0%BB%D0%BD%D0%B0-%D0%BA%D0%B0[…]%BD%D0%B5%D0%B7%D0%B5-trender-%D0%B7%D0%B0-apple-watch-4041mm.
3. It is being decoded wrongly as https://www.dotcms.com/destinations/???????-??????-???-????????-trender-??-apple-watch-4041mm
4. This happens not to work if you forward to a page EXTERNALLY, if you self-reference the site in any way (including using demo.dotcms.com), it appears to work.
5. In the vanity URL configuration, used dotcms.com, and you can see it ends up with an improperly encoded version

Acceptance Criteria

Decoding of write pattern should be sent to the external site

dotCMS Version

23.01.7
23.10.24

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/113992
https://dotcms.slack.com/archives/CSHTYUR7H/p1699379538799279

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[yolabingo]

redirects from Rules using regex backreferences exhibit the same behavior

[binarybasher]

Is there any news or expected LTS release for this fix?

[erickgonzalez]

Hi @binarybasher , one of our top developers is working on this, so we hope to have a fix soon. But it still needs to go through the whole process (merge PR -> Internal QA -> QA) to be included in an LTS release.

[binarybasher]

Thanks @erickgonzalez , do you have any ETA for the LTS release?

Thank you and Happy New Year!

[erickgonzalez]

Hi @binarybasher ,

We hope that by the End of January, this fix will be included in all LTS releases.

Happy New Year.

[erickgonzalez]

Working as it should, now it's being decoded just fine.

[bryanboza]

Fixed, tested on master // Docker // FF

[binarybasher]

Thanks for the updates @erickgonzalez
Do you happen to know which LTS version this is likely to be included in?
Thanks