AW: mod_jk interference with ErrorDocument/Alias on HEAD request

2022-02-16 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello Stefan, the debug output of mod_jk shows at least which route the request is going: [info] jk_handler::mod_jk.c (2968): No body with status=401 for worker=ajp13_worker So it looks like that the code

AW: mod_jk interference with ErrorDocument/Alias on HEAD request

2022-02-15 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello Stefan, Now I got it. Thanks for the clarification :) -Ursprüngliche Nachricht- Von: Stefan Mayr Gesendet: Dienstag, 15. Februar 2022 14:26 An: users@tomcat.apache.org Betreff: Re: mod_jk interference with ErrorDocument/Alias on HEAD request Hello Thomas, Am 15.02.2022 um 11:38

AW: mod_jk interference with ErrorDocument/Alias on HEAD request

2022-02-15 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello Stefan, by spec / RFC, a HEAD request is not allowed to return any body. Greetings, Thomas -Ursprüngliche Nachricht- Von: Stefan Mayr Gesendet: Montag, 14. Februar 2022 23:07 An: users@tomcat.apache.org Betreff: Re: mod_jk interference with ErrorDocument/Alias on HEAD request

AW: mod_jk interference with ErrorDocument/Alias on HEAD request

2022-02-13 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello, the spec https://datatracker.ietf.org/doc/html/rfc7231#page-25 says in chapter 4.3.2: " The HEAD method is identical to GET except that the server MUST NOT send a message body in the response (i.e., the response terminates at the end of the header section)." Greetings, Thomas

AW: mod_jk interference with ErrorDocument/Alias on HEAD request

2022-02-13 Thread Thomas Hoffmann (Speed4Trade GmbH)
Hello, maybe you can try to set an environment variable which skips interpreting the content-length: https://tomcat.apache.org/connectors-doc/reference/apache.html#Advanced%20Environment%20Variables --> JK_IGNORE_CL To get more information, you can also set the logfile and log-level to debug: