-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Neeraj,
On 6/24/14, 1:09 PM, Neeraj Sinha wrote:
> I am using form based authentication (tomcat 7.0.34) and I have
> the implementation of custom realm class which extends RealmBase
> class.
You need to upgrade. There are security updates classifie
Thanks for the response Konstantinos. I'll look into the HSTS header. The
behavior you describe may be what is happening.
Bruce
Sent from my iPad
> On Jun 24, 2014, at 8:51 AM, Konstantin Preißer wrote:
>
> Hi,
>
>> -Original Message-
>> From: Christopher Schultz [mailto:ch...@christ
I am using form based authentication (tomcat 7.0.34) and I have the
implementation of custom realm class which extends RealmBase class. Inside
the getPrincipal() method implementation, I am calling backend service to
save some login details. I need to pass host name to backend (I have 2
application
>>
>> HTTP/1.1 302 Found
>> Set-Cookie: JSESSIONIDSSO=
CF7B7727443A3AAD1AC3AA033E4D98BE; Expires=Thu, 01-Jan-1970 00:00:10 GMT
>> (...)
I filed this issue into bugzilla:
https://issues.apache.org/bugzilla/show_bug.cgi?id=5
Best regards,
Konstantin Kolinko
---
Hi,
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Thursday, June 19, 2014 5:40 PM
> >
> > I haven't followed all of this discussion, but as for deleting a
> > Cookie, I think the problem is that there isn't an explicit
> > "Delete-Cookie" he
Hi,
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Tuesday, June 24, 2014 2:42 PM
> To: Tomcat Users List
> Subject: Re: Browsers suddenly start timing out when accessing port 80 of
> secure site
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim,
On 6/23/14, 4:21 PM, Jim Lindqvist wrote:
> I have I server with Apache and Tomcat through jk_mod and the
> perfonrmance is awful. This is mostly confined to images as far as
> I know, but it is hard to tell.
>
> The images are served from Apa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 6/23/14, 2:30 PM, Bruce Lombardi wrote:
> Moving the SSL port from 8443 to 443 has solved the problem. It
> appears that when the url www.something.net is entered, Firefox
> remembers that this is an SSL site and automatically add the "s