The underlying problem which caused this bug is that query parameters, at least, are not being tagged with any particular encoding. Based on some reading, it’s my understanding that modern Rails versions do correctly indicate the encoding of parameters provided in request bodies (by looking at the C…

Looks like they rejected it: (I submitted it to Rails, and it was rejected because this is fixed in another way in Rails 5. But Discourse is still on Rails 4.)

Specifically here: ASCII comes in two flavors that need to be UTF-8ified. by begrif · Pull Request #30119 · rails/rails · GitHub (link goes to a particular comment). It could be that’s me just going about submitting fixes in the wrong way.

It looks like this is fixed in Rails 5 but it is unclear when we can move Discourse to that (we are currently on Rails 4). There are typically a lot of performance regressions in each new release of Rails that we have to help fix, so it takes some time for us to move.

Well, time for a custom before_filter, I guess.

Now that Discourse is on Rails 5, is it safe to reactivate the slug generation to encoded?

I guess so, based on this reply: [Bild] When slug generation method is encoded, It redirected many times when we open new tab opens in topic bug @Alavi1412 Can you upgrade to latest? This is fixed after we upgraded to Rails 5.1 but is there any benefit to change the …

It’s for SEO and for human consumption. Our community heavily uses Japanese.

Yes, apologies for the delay but it should be 100% working now! Let us know if you run into any issues.

when the slug generation method is changed to “encoding”, the spaces between each two words in the topic titles changes to - and it makes the topic list page very unclean. [k] is it something related to rails or is it solvable by changes to the forum?

It’s a bug that’s been fixed a few hours ago. Update to latest.

Automatische Kodierung der geparsten URL-Parameter

Entwickler

pfaffman (Jay Pfaffman) 27. Oktober 2017 um 16:38 43

See also discussion here: How to replace a string/character in topic title?

Thema		Antworten	Aufrufe
Topic with Japanese in URL doesn't redirect if URL doesn't perfectly match Bug	72	4260	21. Oktober 2019
When slug generation method is encoded, It redirected many times when we open new tab opens in topic Bug	9	5346	16. November 2017
Mods/admins to change topic URL slug (just like in WordPress) Feature	3	1361	4. Dezember 2025
Removing the concept of "slugs" for some languages Feature	27	10178	28. Dezember 2017
Force Lowercase slug URLs when set to "encoded" Support	23	4442	8. Juni 2024

Automatische Kodierung der geparsten URL-Parameter

Verwandte Themen