Disabling normalization of decoding of characters

[SebbeJohansson]

Hi! We have issues with the redirect during normalization of encoded characters (| = %7C etc). This is mainly a big issue on Apple devices it seems like.
We would like to disable the feature completely (we are using nuxt) so as to allow the encoded characters to be in its "pure" form.
For example https://domain.com/klader?series=nordwand%7Cgp -> https://domain.com/klader?series=nordwand|gp
Is this possible some how?

[posva]

This seems to be the current behavior. Note encoding is also handled at the browser level so maybe you are seeing something else changing it

[posva]

I mean that the | is not encoded and that you shouldn't try to control what is encoded or not as it's all part of a spec that needs to be respected for URLs to be valid

[SebbeJohansson]

You are misunderstanding the direction. It gets transformed INTO | during the routing. Not the other way around. I guess it's decoding from uri into characters.

Look at my example and hopefully it's more clear.

To further show the issue, here it is in a production enviroment: https://www.revolutionrace.com/clothing?series=nordwand%7Cgp

Loading that results in an infinite loop that is based on the decoding and redirect that vue router does.

[posva]

I see. Your example confused me because the same URL appears twice like x -> x precisely because the | gets decoded. If I try to edit the comment I see the difference. I think I've seen that issue reported in Nuxt repo in the past. The encoding of Vue router is intentionally consistent with what the spec expect so the | always appearing as | is a feature

[SebbeJohansson]

Okay good. Sorry that it was confusing.
As I specified, the "redirect" or whatever is technically done causes an infinite redirect in nuxt that they are not planning to change or counter, hence why I'm asking here!

I understand the want for "pretty" URLs, but this is causing pages not to work at all (especially on Apple devices). I know this is an issue for many companies, but I understand the reluctance to change it in the application.

Is a setting/workaround completely impossible/out of the question? 😅 For us currently it means that a subset of our links (coming primarily from stuff like newsletters) are completely broken.

Let me know if I should create another issue on the nuxt GitHub instead.

[posva]

I wouldn’t create another issue but instead search for similar ones. I am almost sure the end cause was related till user code and could be fixed