Some clients do not understand how to use UTF-8, and execute a request to for example /thumbs/400%C3%83%C2%97400%C3%83%C2%97contain/news, which contains à instead of the expected ×. I do not know why %83%C2 is inserted in the URL (it is some sort of Python based external scanner...), but I do believe this code should be robust enough to not throw a warning when this happens. With this change the raw parameters are checked for existence before being used, allowing for a sane fallback.
I do not believe the CI failures are related to this change.
Solves a
Warning: Undefined array key 1
notice.Some clients do not understand how to use UTF-8, and execute a request to for example
/thumbs/400%C3%83%C2%97400%C3%83%C2%97contain/news
, which containsÃ
instead of the expected×
. I do not know why%83%C2
is inserted in the URL (it is some sort of Python based external scanner...), but I do believe this code should be robust enough to not throw a warning when this happens. With this change the raw parameters are checked for existence before being used, allowing for a sane fallback.I do not believe the CI failures are related to this change.