Re^2: UTF-8 and PSGI/Starman vs. CGI

Probably your setup is broken all the way through and it only acts correctly in the CGI/Apache level because it's broken in the same ways in the same places

Ugh. That's a possibility I really don't want to think about, because the webapp in question isn't a small, in-house project, it's a very large open source project (Koha, to be specific) and we really don't have the time or manpower to do a thorough audit of how it handles character encodings.

Still, double-checking the database settings and taking a look at uWSGI are low-hanging fruit which can easily fit into the schedule, so I'll at least cross my fingers and try those before doing anything drastic. Thanks!

Comment on Re^2: UTF-8 and PSGI/Starman vs. CGI

Replies are listed 'Best First'.
Re^3: UTF-8 and PSGI/Starman vs. CGI by Your Mother (Archbishop) on Mar 22, 2018 at 14:42 UTC
Yeah. No fun at all if so. It was so for us and took a lot of work to fix. I don't know if this is the right place, but in case you haven't seen it -> Charsets/Encoding in Koha. I still recommend uWSGI but I don't think it will help with encoding problems, just performance and stability.	[reply]
Re^4: UTF-8 and PSGI/Starman vs. CGI by dsheroh (Monsignor) on Mar 23, 2018 at 11:07 UTC
I have seen that page before, but it can't hurt to go through and double-check all of those settings for correctness. We already discovered that the db had a default latin1 encoding and are in the process of rebuilding it as utf8mb4, but there might be something else there that's also been missed.	[reply]