We have a bunch of Tomcat 8.0.15, Apache 2.2.29 and mod_jk 1.2.40 (win2003 serv) In the http response status text we have "200 ACT". Is not a standart http 1.1 rfc "200 OK". It doesn't affect on a normal work, but response is really weird... Also tested on a clean-default configuration tomcat8-apache2.4(win7) - the same result. In the mod_jk debug log we have: [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): received from ajp13 pos=0 len=69 max=8192 [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0000 04 00 C8 00 03 41 43 54 00 00 02 00 0D 43 61 63 - .....ACT.....Cac [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0010 68 65 2D 43 6F 6E 74 72 6F 6C 00 00 19 70 72 69 - he-Control...pri [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0020 76 61 74 65 2C 6E 6F 2D 63 61 63 68 65 2C 6E 6F - vate,no-cache,no [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0030 2D 73 74 6F 72 65 00 A0 01 00 09 69 6D 61 67 65 - -store.....image [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0040 2F 70 6E 67 00 00 00 00 00 00 00 00 00 00 00 00 - /png............ [debug] ajp_unmarshal_response::jk_ajp_common.c (705): status = 200 [debug] ajp_unmarshal_response::jk_ajp_common.c (712): Number of headers is = 2 [debug] ajp_unmarshal_response::jk_ajp_common.c (768): Header[0] [Cache-Control] = [private,no-cache,no-store] [debug] ajp_unmarshal_response::jk_ajp_common.c (768): Header[1] [Content-Type] = [image/png] Normal response is like: [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): received from ajp13 pos=0 len=100 max=8192 [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0000 04 00 C8 00 02 4F 4B 00 00 04 00 04 45 54 61 67 - .....OK.....ETag [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0010 00 00 17 57 2F 22 31 38 36 39 35 2D 31 34 31 33 - ...W/"18695-1413 [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0020 33 39 33 38 32 34 35 34 33 22 00 A0 05 00 1D 57 - 393824543".....W [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0030 65 64 2C 20 31 35 20 4F 63 74 20 32 30 31 34 20 - ed,.15.Oct.2014. [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0040 31 37 3A 32 33 3A 34 34 20 47 4D 54 00 A0 01 00 - 17:23:44.GMT.... [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0050 08 74 65 78 74 2F 63 73 73 00 A0 03 00 05 31 38 - .text/css.....18 [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0060 36 39 35 00 00 00 00 00 00 00 00 00 00 00 00 00 - 695.............
I had noticed this as well in December and fixed it in commit r1645248. This will be part of the very soon to be released next version of TC 8. The problem does not exist in TC 7 or before. Thanks for reporting it. Rainer
Thanks a lot! But in the tomcat 8.0.16-dev changelog have not added... http://ci.apache.org/projects/tomcat/tomcat8/docs/changelog.html Waiting for a while... *** This bug has been marked as a duplicate of bug 57347 ***
The change is contained in the changelog of the forthcoming release: + <fix> + <bug>57347</bug>: AJP response contains wrong status reason phrase + (rjung) + </fix> The CI build is older, dated Dec 1st. Thanks for linking to the original BZ ticket. Forgot about that one.