There is an included diagnostic module for this that is easy to activate and produces plaintext output:
http://publib.boulder.ibm.com/httpserv/manual24/mod/mod_net_trace.html
If you have difficulty reading the hexdump-like output, the file can be parsed by downloading the IHS mustgather "ihsdiag" and running the "ParseNetTrace" sub-tool. It will create many files in the filesystem for data sent/recvd on different connections.
http://publib.boulder.ibm.com/httpserv/ihsdiag/install.html
If you can't find the issue with the 400, the error_log and nettrace could be analyzed quickly in a support case.
#Support#SupportMigration#WebSphereHTTPServer