netty 4.0.41.Final /bad-request

37 views

Skip to first unread message

Artem Kalinovskiy

unread,

Oct 26, 2016, 6:54:58 AM10/26/16

to Netty discussions

We use Play framework wich based on netty in our production environment. After switching to a new version with netty 4.0.41.Final we've faced with some problems. There were a lot of '/bat-request' messages in our logs:

INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty
INFO  application - Bad request from /xxx.xxx.xxx.xxx on GET /bad-request : status - 400 text is empty

We added some extra logging to HttpRequestDecoder.createMessage(String[] initialLine) method through javaagent. Problem `initialLine` looks like:

["/some-real-url", "HTTP/1.1", ""]

It looks like `readerIndex` at request's `ByteBuf` is misplaced but I am not sure.