https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
Remy Maucherat changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #4 from Remy Mauchera
https://bz.apache.org/bugzilla/show_bug.cgi?id=69752
--- Comment #3 from Remy Maucherat ---
Indeed, it definitely logs what is deployed, so it will be obvious there is
something to fix. If we try to fix these kind of items, then I am sure we will
run into someone reporting a regression because th
https://bz.apache.org/bugzilla/show_bug.cgi?id=69752
--- Comment #2 from Mark Thomas ---
Generally, Tomcat doesn't prevent valid but potentially foolish configuration
settings. Such "protection" would add a significant amount of bloat to the
codebase and, given the size and diversity of the insta
https://bz.apache.org/bugzilla/show_bug.cgi?id=69752
--- Comment #1 from Don't show my email ---
NOTE:
The Tomcat docs for the HOST Element are not naming what happens with an empty
option is used, nor is there a security risk advise for this case. I suggest to
change this for all TC versions i
https://bz.apache.org/bugzilla/show_bug.cgi?id=69752
Bug ID: 69752
Summary: HOST appBase = "" accepted as valid option
Product: Tomcat 9
Version: 9.0.102
Hardware: PC
OS: Linux
Status: NEW
Severity: major
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #3 from Nagendra ---
When a request is processed synchronously, Tomcat works fine as follows.
1. Handles the request and sends a response.
2. Waits for the next request from the same client for a duration defined by
keepAliveTimeou
