Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Session disconnect
Date: Mon, 2 Feb 2004 09:48:48 -0500
Message-ID: <B5B54F0E3DB0B444A497BD6DC11226F4B7B1@exchange.hupklaw.net>
Thread-Topic: Session disconnect
Thread-Index: AcPonPxXeVOqpUP5QySlBHOFuCUyhAA/oDnA
From: "Mark Tebong" <mtebong@hupk.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>

I don't think it has anythin to so with cookies because sessions don't
use paths.=20

-----Original Message-----
From: Antonio Fiol Bonnin [mailto:fiol.bonnin@terra.es]
Sent: Sunday, February 01, 2004 3:30 AM
To: Tomcat Users List
Subject: Re: Session disconnect


Mark Tebong wrote:

>I have it configured so that when a request for a URL (say
www.mydom1.com) comes in, the proxy sends it to 192.168.11.211/mydom1.=20
> =20
>

>When I access the pages of the site that use the session thru
www.mydom1.com, I get an exception. When I access it through
192.168.11.211/mydom1, it works fine.
> =20
>

>I looked at the tomcat logs and I saw that the session was
disconnecting when you used the proxy.=20
> =20
>

Hi,

No idea about the "images" stuff, but...

Could you be having trouble because of the "path" attribute of the
cookies?

If Tomcat (or your webapp) is setting it to "/mydom1" then browsers will

not send it when accessing "/".

HTH,

Antonio Fiol

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org