Am Freitag, 22. Dezember 2017 21:19:10 UTC+1 schrieb Graham Dumpleton: > Write it to a file on the file system, don't use print() to verify the > value. > > When you use print() the Apache logging system which is processing it will > do escaping of stuff. > > If after writing a to a file you still see an issue, then provide updated > results. >
Thank you for your reply. You are right, Apache's logging system was responsible for the "double-encoding" and the test system actually works correctly. The actual problem I see in the production system and my development system is the opposite from what I described here: PATH_INFO gets decoded, e.g. "f%C3%B6o" becomes ['0x66', '0xf6', '0x6f'], while on the test system it's ['0x66', '0xc3', '0xb6', '0x6f'] (which is correct from what I understand). Anyway, I suspect a problem on my end and will have to dig deeper to find the difference between the development environment and the test case. - Sebastian -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
