When serving page with URIs containing utf8 chars with fast_404_path_check(), depending on server configuration, queries might return false even if given path does exist in backend, but was rewriten to utf-8 enabled string.
To prevent this we should explicitly set database connection charset.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | utf8-db-connection-1635446-10.patch | 690 bytes | ragnarkurm |
| #9 | utf8-db-connection-1635446-9.patch | 699 bytes | ragnarkurm |
| #6 | utf8-db-connection-1635446-5.patch | 597 bytes | madhavvyas |
| #1 | utf8-db-connection-1635446-1.patch | 1013 bytes | GrzegorzNowak |
Comments
Comment #1
GrzegorzNowak commentedattaching sample patch agains 6.x-1.x branch
Comment #2
soyarma commentedWhat possible reprecussions could this have if the data is not UTF-8
Comment #3
madhavvyas commentedComment #5
madhavvyas commentedComment #6
madhavvyas commentedPatch re rolled #1
Comment #7
madhavvyas commentedComment #9
ragnarkurm commentedUpgraded the patch.
It is for 7x.1.x branch.
Dev branch seems to be abandoned.
Comment #10
ragnarkurm commentedHere is updated version.
We need UTF also for redirect checking.
Comment #11
ragnarkurm commentedChanging the version to 7.x-1.5,
since working patches are for that version.
They can be back-ported if needed.
Comment #12
ragnarkurm commented