https://bz.apache.org/bugzilla/show_bug.cgi?id=66535
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=66535
--- Comment #3 from Mark Thomas ---
This is the commit that introduced maxValidTime
https://github.com/apache/tomcat/commit/4364cbc8d1f5cc6dbe9be0132d92e593ef67346c
Having looked at the commit, I think the intention could be taken to be eithe
https://bz.apache.org/bugzilla/show_bug.cgi?id=66535
--- Comment #2 from Alex West ---
If this is intended behavior, the documentation should be updated to explain
that the configuration setting has a bearing on the amount of time it may take
to transfer WAR files over a slow network, or many nod
https://bz.apache.org/bugzilla/show_bug.cgi?id=66535
--- Comment #1 from Alex West ---
Although this may be 'intended' behavior, the code would lead me to believe
that the developers intended this to be a check on whether the file was 'valid'
and whether it had been 'idle' for some time.
I assum