On 20/10/2020 10:10, Michael Osipov wrote:
> Folks,
>
> I have seen recently entried like this on our access logs:
>> 2020-10-19T20:00:05.591 [null] xyz - "-" 400 - 0
>> 2020-10-19T20:00:05.591 [null] abc- "-" 400 - 0
>> 2020-10-19T20:00:05.592 [null] abc - "-" 400 - 0
>> 2020-10-19T20:00:05.593 [null] abc - "-" 400 - 0
>> 2020-10-19T20:00:05.616 [null] abc - "-" 400 - 0
>
> with pattern:
>> %{yyyy-MM-dd'T'HH:mm:ss.SSS}t [%I] %h %u "%r" %s %b %D
>
> While I am quite certain that these ary "security" scans at work
> I wonder why RequestInfo#getWorkerThreadName() is null.
> Is the request rejected because it is malformed because before it is
> handled to a worker?
Have you tried looking at the source code? Callers of
RequestInfo.setWorkerThreadName() are likely to be enlightening.
> I am not sure whether "info != null &&
> info.getgetWorkerThreadName() != null" would be the right change here.
That would address the symptom. There may be a better fix that addresses
(or at least gets closer) to the cause.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
