Tweet
This might help some users.
Users with search word logging turned on might from time to time notice what appear to be corrupted words in the search log file. Like,
2006-01-22, 00:55:12, 212.0.129.65, "'-.- -'- 1-"
2006-05-15, 16:44:56, 212.0.129.65, "3-c-3-"
2006-06-14, 21:56:27, 212.0.129.65, "9-1- -j-"
Initially you might think this is a software bug or corruption or someone if trying to hack your search function.
The real reason is more mundane. Your search form is probably in a single byte English character set but some users are searching in double byte (Unicode) languages. e.g. Arabic.
The 'corruption' is actual just the Arabic words being displayed in a single byte English font. Which is normal if you aren't using Unicode.
Users with search word logging turned on might from time to time notice what appear to be corrupted words in the search log file. Like,
2006-01-22, 00:55:12, 212.0.129.65, "'-.- -'- 1-"
2006-05-15, 16:44:56, 212.0.129.65, "3-c-3-"
2006-06-14, 21:56:27, 212.0.129.65, "9-1- -j-"
Initially you might think this is a software bug or corruption or someone if trying to hack your search function.
The real reason is more mundane. Your search form is probably in a single byte English character set but some users are searching in double byte (Unicode) languages. e.g. Arabic.
The 'corruption' is actual just the Arabic words being displayed in a single byte English font. Which is normal if you aren't using Unicode.