-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Alfred,
On 6/15/20 09:45, Alfred Bakia wrote: > Thanks, Chris. To respond to your remarks: > > 1) The warnings, "AJP13 protocol: Reuse is set to false", are > being logged by Tomcat (in the Tomcat AJP connector logs). Weird. I can't find that string anywhere in code or other files in Tomcat, but its right there in mod_jk: ./native/common/jk_ajp_common.c: jk_log(l, JK_LOG_WARNING, "(%s) AJP13 protocol: Reuse is set to false", Are you sure you are looking at the right log file? > 2) As I mentioned earlier, the versions and settings of the > servers (and their respective IIS web servers) are the same. > > In any case I have discovered "how" the warning occurs. It is > indeed triggered by the REST API. > > The culprit is a REST request in the form: > > http://www.ourdomain.com/api/srv2/exercises/93/1431/26346/ping > > It is a POST request and "ping" is a custom REST method. It is > just a ping, so the status code of the response is 204 ("No > Content"). A 204 response should not cause any problem. > I can confirm that every ping request results in the warning > "AJP13 protocol: Reuse is set to false" being written to Tomcat's > connector logs. > > Researching this on the web, I found the suggestion to add > allowedRequestAttributesPattern=".*" to the AJP connector in > server.xml. > > Is this a viable solution? This has nothing to do with your REST API. This is a change made to recent versions of Tomcat that may require you to allow certain non-standard variables to be passed-over from your web server to Tomcat via AJP. If your "ping" REST API is requiring some information to be passed from the web server to Tomcat and you are seeing errors on the Tomcat side, then you may have to fiddle with the allowedRequestAttributesPattern. Setting the value to ".*" is a violation of sane security policy. But I see no evidence that your "Reuse is set to false" error is related (yet) to the allowedRequestAttributesPattern. If you see errors in the Tomcat log, please post them and we'll see. The allowedRequestAttributesPattern wasn't added to Tomcat until 9.0.31 so if you really are running 9.0.21, then adding allowedRequestAttributesPattern will accomplish nothing. - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7pB3wACgkQHPApP6U8 pFg97w//T8XVtWlic/x/nUJHZUXfDs99Ou8cKcSFFI/AbBldd5k8vSxCTKg40wON 3bUooWG5GWZhVRNHH2JH0eyiKqhLmDtAzdnSp7xAkAW2fAZ2Zlv0VLb0AzJCTqRg e1Nd9R9Ii9mjcSU5+M2WrNSourUhOT0FVYaqpvlaN89XyetHSuVIUladDuwM8kFN 3ngAtkgmIYfxXcqIPXjoNZ+s8cr1MB0qk+KkiXyOCb8XgfmZUkBMRncgqMAgEff5 p6Z/1jGVv0+S7E0+HV1yqJpakiGjVswfIjbc2s89YnVL6bvyBqUnJl4HrmOHY0bV d3O/NQ3+vZ/Kma4e84TI5QKQx0KvQj0oBH41fFl0WmPjraKjGMTTfMCy9BjvLwdf hbTEbZaBRvn7Tr+iR5ksrvaJTxZD1ABMb7o0uksCsPQO8h3tl3s7L5O4g0P3+7kV /SiqDD+WyqkhmJuX86Y3MtSeMUTsg9RiXOZLLGF59TOZFeso/2O+OWYU/uImXw2X opWW38Vowhn8O9a94RbRA67EvJFiLdWwTDoLlnVP0ZxGkdOIow0EQWfnCDKaBXOd l+BdTG7zPbU8I3bw00cXGytyCYENt9uIZJ/XVVkyC2EAFAbEArVjWR0ocZT4W6zQ bCc5vbHFJnNvCRh8jeSl9ORSzBFzYPt0B1kvSMkNE0U7y7mU74c= =8kiV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
