I'm running TC 9.0.53 on my Windows 11 dev environment. I do not need
to have SSL/TLS implemented locally. So all calls are http, not https,
if that makes a difference here. For several years on various projects
I work on, I'll get into a state where I get an immediate 408 (too much
time expired for login) when I submit a login. There is no time delay.
I click Sign-In to get the form, key the id/pw and select login, and get
the response. Interestingly, if I submit an incorrect id/pw, I get the
normal login failed response, not the 408. Sometimes if I switch
between Firefox and Chrome, the problem goes away. It won't recur for a
while. But sooner or later, it's back. Currently it's failing on both
Chrome and Firefox. I'm not doing anything weird in the login process.
Standard form-based login I've used for years. But it'll randomly start
failing this way. Then just as quickly as it came on, it'll start
working again and maybe not fail for days or weeks.
I saw some post about setting a "Secure" cookie to false. Not much
other info. I added that to the top of the login form page. No change.
Is this a known issue? Is there a work-around (other than possibly
adding SSL/TLS to my dev environment)?
Thx
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
