Cookies/Session Issues

2006-10-10 Thread Michael Andreas Omerou 
Hello,

We are having a web app which uses session over both plain and SSL
connections.

The very first time that someone accesses our initial page (i.e. never
before visited the site so that there is no session cookie on his/her
browser, not even an expired one) the server creates a session and sends the
appropriate cookie to the browser.  The problem is that for some reason the
created session is destroyed immediately after the response for the page
commits (i.e. after the page finishes loading).  

At this time, I have a cookie containing the JSESSIONID of an expired
session.  If I refresh the page or close and open later, etc. the request to
the server contains the cookie sent initially and of course, since the
server expired the session it sends back a new JSESSIONID.  This time, the
second one, the server does not expire the session.

My question is: what is causing the session to expire the very first time
since it has just been created and why is this fixed on subsequent requests?
What can I do so that when a session is instantiated it is maintained?

Please note that I experience exactly the same behaviour the very first time
I access a page over SSL.
 
Thanks in advance for your help.

Rgds,
Michael


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-20 Thread Michael Andreas Omerou 
Hi Guys,

First of all thanks for your assistance so far.  I played a lot trying to
remove the response.setHeader() and leaving meta tags only in my code, then,
removing meta-tags and leaving response.setHeader(), I tried all possible
combinations of meta tags,etc. 

What I ended up and thought of letting you know is that the problem was
caused by using response.setHeader().  By removing these statement and
leaving the relevant Cache-control, Expires and Pragma meta-tags in the
code, all works fine.

It is indeed very strange to notice this, it should not really make any
difference and cause problems to FireFox specifically.

Once more thanks for your support.

Michael
-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 17 February 2006 07:38
To: 'George Sexton'; 'Tomcat Users List'
Cc: [EMAIL PROTECTED]; 'Joey Geiger'; [EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Thanks for the suggestion George.

I don't think is the proxy because IE and other browsers work 
with the same proxy so I don't see why FireFox should not.  I 
will try your suggestion though and let you know the outcome.

As far as other suggestions, no. 1 is particularly interesting 
and will try it, as well as no.2.  For your third suggestion I 
explained to you why I am doing it.

As far as the X-Cache: MISS, etc. these appear with IE as well 
but IE works so it can't be the problem.

Michael

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED]
Sent: 17 February 2006 05:22
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; 'Joey Geiger'; [EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Since I regularly use Firefox and sessions I'm pretty sure that there 
is really nothing unique to that combination that is causing the 
problem. It could be the proxy server below is causing the issue. The 
obvious thing to do would be to try from a different network 
without a 
proxy server and see if your issue clears up.

I would also recommend that you do a little cleanup on your 
HTML pages 
and see if there is some effect on the issue. The specific things I 
would fix in your HTML are:

1)No DocType, causing the page to render in Quirks mode. FYI, this
will cause differences in the box model which will result in 
IE 6.0 and 
FireFox/Mozilla displaying pages very differently.

2)No Content type/charset meta in the header.

3)You have a duplicate HEAD block in the bottom of your page.

Your reference to the cache-control entry:


 Cache-Control: max-age=0

Doesn't appear in my browser. I would suspect that its being added by 
your proxy server.

 X-Cache: MISS from proxy01.spidernet.net
 X-Cache-Lookup: MISS from proxy01.spidernet.net:83

I would also say that if you're going to use the addHeader() 
to put in 
cache/pragma entries that you should not use the META tags.





George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

 -Original Message-
 From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 16, 2006 3:38 PM
 To: 'Tomcat Users List'
 Cc: [EMAIL PROTECTED]; 'George Sexton'; 'Joey Geiger'; 
 [EMAIL PROTECTED]
 Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
 
 Dear all,
 
 Thanks for your replies to my problem.  However, I think the 
 discussion has been diverted into a debate totally
irrelevant to the
 issue.
 
 As far as Chuck's question whether this could be related to
the popup,
 this is not the case as the problem happens on other pages 
too, even 
 on index.jsp (first page)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JSP compilation error in Tomcat 5.5 using type Vector

2006-02-20 Thread Michael Andreas Omerou 
 Can we have the code that causes this error?

-Original Message-
From: Thibaut Nicolas [mailto:[EMAIL PROTECTED] 
Sent: 20 February 2006 16:33
To: users@tomcat.apache.org
Subject: JSP compilation error in Tomcat 5.5 using type Vector

Hi all,

I have a problem while trying to migrate an application from 
Tomcat 4.1 to Tomcat 5.5.
I get a JasperException when tomcat try to compile a JSP :
The method add(String) is undefined for the type Vector The 
method iterator() is undefined for the type Vector I've put 
the complete trace at the end of the message.

I'm using tomcat 5.5.15. I've tried with 2 version of Java 
(JAVA_HOME set to 1.5.0_06 or 1.4.2_04 (with compat package)).
I've also tried on 2 different platforms : solaris and linux.
The problem is always the same. It seems that the compiler is 
trying to compile the generated java file with a java 1.1 
compatibility.
I've read in the documentation that the JDT compiler should work with a
1.4 compatibility by default (I've tried to set the servlet 
init parameters compilerSourceVM and compilerTargetVM without success).

I've found a workaround that consist in using javac compiler 
instead of JDT compiler but I'd prefer using JDT compiler.

Can someone help me and tell me what I'm doing wrong ?

Thanks in advance

Thibaut




exception

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 4 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method add(String) is undefined for the type Vector

An error occurred at line: 4 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method add(String) is undefined for the type Vector

An error occurred at line: 11 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method iterator() is undefined for the type Vector


org.apache.jasper.servlet.JspServletWrapper.handleJspException(
JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletW
rapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.
java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


root cause

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 4 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method add(String) is undefined for the type Vector

An error occurred at line: 4 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method add(String) is undefined for the type Vector

An error occurred at line: 11 in the jsp file: /jsp/Test.jsp 
Generated servlet error:
The method iterator() is undefined for the type Vector


org.apache.jasper.compiler.DefaultErrorHandler.javacError(Defau
ltErrorHandler.java:84)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDisp
atcher.java:328)
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompile
r.java:409)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:297)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
org.apache.jasper.JspCompilationContext.compile(JspCompilationC
ontext.java:563)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletW
rapper.java:303)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.
java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-16 Thread Michael Andreas Omerou 
Dear all,

Thanks for your replies to my problem.  However, I think the discussion has
been diverted into a debate totally irrelevant to the issue.

As far as Chuck's question whether this could be related to the popup, this
is not the case as the problem happens on other pages too, even on index.jsp
(first page)

Regarding Filip's email and monitoring HTTP Headers I am impressed that it
seems to work for you.  I run FireFox on Windows XP Pro SP2 and what happens
is that when a page finishes loading, the session expires on the server.
When the user/browser requests another page the correct session id is sent
from the browser but the server detects that this session id sent is no more
valid (expired) and so we have a timeout.  However, this behaviour, only
occurs with FireFox.   I tried it from another PC with XP Pro SP2 too but
the problem is the same.  With IE, NetScape and Opera all is ok. 

 

I want to emphasize that this behaviour does not happen only when switching
from SSL to non-SSL or vice versa.  Even if I try to access pages such as
the About Us or the Contact Us the session expires again.  However, in that
case the problem is not visible to the user since those pages do not
contain any session specific data so even with a new session it is ok.  Try
the following though and you will see what I mean.  On tophotelchoices.com
do a search for a hotel.  Let the results be displayed and then, go to the
About Us page.  Then, click your browser's back button and instead of going
back to the search results you get a timeout (if you get search results it
will be from browser's cache, do a reload and you will get timeout).

Monitoring the HTTP headers for both IE and Firefox using HttpAnalyzer for
IE and LiveHttpHeaders for Firefox gives the following:
1) IE

(Request-Line):GET http://www.tophotelchoices.com/ HTTP/1.1
Accept:*/*
Accept-Language:en-gb
Accept-Encoding:gzip, deflate
User-Agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; InfoPath.1)
Host:www.tophotelchoices.com
Proxy-Connection:Keep-Alive
Pragma:no-cache
Cookie:JSESSIONID=6F187E9E698F5D81A09DF6AD0D25115D

(Status-Line):HTTP/1.0 200 OK
Date:Thu, 16 Feb 2006 22:09:18 GMT
Server:Apache/1.3.33 (Unix) mod_jk/1.2.15
Cache-Control:no-cache
Pragma:no-cache
Expires:Wed, 31 Dec 1969 23:59:59 GMT
Content-Type:text/html;charset=UTF-8
X-Cache:MISS from proxy01.spidernet.net
X-Cache-Lookup:MISS from proxy01.spidernet.net:83
Proxy-Connection:close

2) FIREFOX:
GET http://www.tophotelchoices.com/index.jsp HTTP/1.1
Host: www.tophotelchoices.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=
0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Proxy-Connection: keep-alive
Referer: http://www.tophotelchoices.com/timeout.jsp
Cookie: JSESSIONID=3849A82D2F9B6991FE41073D771D1358
Cache-Control: max-age=0

HTTP/1.x 200 OK
Date: Thu, 16 Feb 2006 22:12:27 GMT
Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
Cache-Control: no-cache
Pragma: no-cache
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Content-Type: text/html;charset=UTF-8
X-Cache: MISS from proxy01.spidernet.net
X-Cache-Lookup: MISS from proxy01.spidernet.net:83
Proxy-Connection: close

Obviously, the response is the same in both cases, however, for FireFox the
important difference I see in Request is the one saying Cache-control:
max-age=0 and also, the Keep-Alive value 300. I do not think the Keep-Alive
value is the problem, however, the Cache-Control: max-age=0 is suspicious.
In my code I have response.setHeader(Cache-Control,no-cache) but I think
this is different.  Does anyone have a clue what the max-age:0 is doing?

Your help will be greatly appreciated.


Thanks and regards,
Michael

-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 22:16
To: Tomcat Users List
Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)

George Sexton wrote:
 Does the code transparently create a new JSessionID value then?

George,
you might wanna rethink your comments, they don't shine any 
light on the issue and they for sure don't state any facts, 
let me prove you I am right. Below is the headers I tracked 
with LiveHttpHeaders, as you can see, JSESSIONID remains 
exactly the same in the browser request when the switch from 
HTTP to HTTPS happens.
This is Firefox on Fedora 4. The site works fine.

This must be a browser issue, can you tell us a little bit 
more about what version and platform your browser is on.

1. Request to the home - non secure

http://www.tophotelchoices.com/
GET / HTTP/1.1
Host: www.tophotelchoices.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1)
Gecko/20060124 Firefox/1.5.0.1
Accept:

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-16 Thread Michael Andreas Omerou 
This is really an old thing I read somewhere that IE might not respond to
the top headers so the only way to force IE to work as you want it to (no
caching) was to do this (put one more header at the end).  Back at that time
(IE 5 was used with 6 not being released yet) this solved me many problems
so since then I use this trick it in my code whenever I do not want caching.

Michael 

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: 17 February 2006 04:42
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Just out of curiousity, why do your pages have two HEAD blocks 
(one at the top, and one at the bottom of the page)?

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

 -Original Message-
 From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 16, 2006 3:38 PM
 To: 'Tomcat Users List'
 Cc: [EMAIL PROTECTED]; 'George Sexton'; 'Joey Geiger'; 
 [EMAIL PROTECTED]
 Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
 
 Dear all,
 
 Thanks for your replies to my problem.  However, I think the 
 discussion has been diverted into a debate totally 
irrelevant to the 
 issue.
 
 As far as Chuck's question whether this could be related to 
the popup, 
 this is not the case as the problem happens on other pages too, even 
 on index.jsp (first page)
 
 Regarding Filip's email and monitoring HTTP Headers I am impressed 
 that it seems to work for you.  I run FireFox on Windows XP Pro SP2 
 and what happens is that when a page finishes loading, the session 
 expires on the server.
 When the user/browser requests another page the correct 
session id is 
 sent from the browser but the server detects that this 
session id sent 
 is no more valid (expired) and so we have a timeout.  However, this 
 behaviour, only
 occurs with FireFox.   I tried it from another PC with XP Pro 
 SP2 too but
 the problem is the same.  With IE, NetScape and Opera all is ok. 
 
  
 
 I want to emphasize that this behaviour does not happen only when 
 switching from SSL to non-SSL or vice versa.  Even if I try 
to access 
 pages such as the About Us or the Contact Us the session expires 
 again.
 However, in that
 case the problem is not visible to the user since those 
pages do not 
 contain any session specific data so even with a new session 
it is ok.  
 Try the following though and you will see what I mean.  On 
 tophotelchoices.com do a search for a hotel.  Let the results be 
 displayed and then, go to the About Us page.  Then, click your 
 browser's back button and instead of going back to the 
search results 
 you get a timeout (if you get search results it will be from 
browser's 
 cache, do a reload and you will get timeout).
 
 Monitoring the HTTP headers for both IE and Firefox using 
HttpAnalyzer 
 for IE and LiveHttpHeaders for Firefox gives the following:
 1) IE
 
 (Request-Line):GET http://www.tophotelchoices.com/ HTTP/1.1
 Accept:*/*
 Accept-Language:en-gb
 Accept-Encoding:gzip, deflate
 User-Agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
 .NET CLR 1.1.4322; InfoPath.1) Host:www.tophotelchoices.com 
 Proxy-Connection:Keep-Alive Pragma:no-cache 
 Cookie:JSESSIONID=6F187E9E698F5D81A09DF6AD0D25115D
 
 (Status-Line):HTTP/1.0 200 OK
 Date:Thu, 16 Feb 2006 22:09:18 GMT
 Server:Apache/1.3.33 (Unix) mod_jk/1.2.15 Cache-Control:no-cache 
 Pragma:no-cache Expires:Wed, 31 Dec 1969 23:59:59 GMT
 Content-Type:text/html;charset=UTF-8
 X-Cache:MISS from proxy01.spidernet.net X-Cache-Lookup:MISS from 
 proxy01.spidernet.net:83 Proxy-Connection:close
 
 2) FIREFOX:
 GET http://www.tophotelchoices.com/index.jsp HTTP/1.1
 Host: www.tophotelchoices.com
 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; 
rv:1.7.12)
 Gecko/20050919 Firefox/1.0.7
 Accept:
 text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
,text/plain;q=
 0.8,image/png,*/*;q=0.5
 Accept-Language: en-gb,en;q=0.5
 Accept-Encoding: gzip,deflate
 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive: 300
 Proxy-Connection: keep-alive
 Referer: http://www.tophotelchoices.com/timeout.jsp
 Cookie: JSESSIONID=3849A82D2F9B6991FE41073D771D1358
 Cache-Control: max-age=0
 
 HTTP/1.x 200 OK
 Date: Thu, 16 Feb 2006 22:12:27 GMT
 Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
 Cache-Control: no-cache
 Pragma: no-cache
 Expires: Wed, 31 Dec 1969 23:59:59 GMT
 Content-Type: text/html;charset=UTF-8
 X-Cache: MISS from proxy01.spidernet.net
 X-Cache-Lookup: MISS from proxy01.spidernet.net:83
 Proxy-Connection: close
 
 Obviously, the response is the same in both cases, however, for 
 FireFox the important difference I see in Request is the one saying 
 Cache-control:
 max-age=0 and also, the Keep-Alive value 300. I do not think the 
 Keep-Alive value is the problem, however, the Cache-Control: 
max-age=0 
 is suspicious.
 In my code I have
 response.setHeader(Cache-Control,no-cache) but I

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-16 Thread Michael Andreas Omerou 
Thanks for the suggestion Wade but I really did what you are saying and
headers reach the server correctly.

Michael 

-Original Message-
From: Wade Chandler [mailto:[EMAIL PROTECTED] 
Sent: 17 February 2006 05:16
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

  Monitoring the HTTP headers for both IE and
 Firefox using
  HttpAnalyzer for
  IE and LiveHttpHeaders for Firefox gives the
 following:
  1) IE
  
  (Request-Line):GET http://www.tophotelchoices.com/
 HTTP/1.1
  Accept:*/*
  Accept-Language:en-gb
  Accept-Encoding:gzip, deflate
  User-Agent:Mozilla/4.0 (compatible; MSIE 6.0;
 Windows NT 5.1;
  SV1; .NET CLR
  1.1.4322; InfoPath.1)
  Host:www.tophotelchoices.com
  Proxy-Connection:Keep-Alive
  Pragma:no-cache
  Cookie:JSESSIONID=6F187E9E698F5D81A09DF6AD0D25115D
  
  (Status-Line):HTTP/1.0 200 OK
  Date:Thu, 16 Feb 2006 22:09:18 GMT
  Server:Apache/1.3.33 (Unix) mod_jk/1.2.15 Cache-Control:no-cache 
  Pragma:no-cache Expires:Wed, 31 Dec 1969 23:59:59 GMT
  Content-Type:text/html;charset=UTF-8
  X-Cache:MISS from proxy01.spidernet.net X-Cache-Lookup:MISS from 
  proxy01.spidernet.net:83 Proxy-Connection:close
  
  2) FIREFOX:
  GET http://www.tophotelchoices.com/index.jsp
 HTTP/1.1
  Host: www.tophotelchoices.com
  User-Agent: Mozilla/5.0 (Windows; U; Windows NT
 5.1; en-GB; rv:1.7.12)
  Gecko/20050919 Firefox/1.0.7
  Accept:
 

text/xml,application/xml,application/xhtml+xml,text/html;q=0.9
 ,text/plain;q=
  0.8,image/png,*/*;q=0.5
  Accept-Language: en-gb,en;q=0.5
  Accept-Encoding: gzip,deflate
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
  Keep-Alive: 300
  Proxy-Connection: keep-alive
  Referer:
 http://www.tophotelchoices.com/timeout.jsp
  Cookie:
 JSESSIONID=3849A82D2F9B6991FE41073D771D1358
  Cache-Control: max-age=0
  
  HTTP/1.x 200 OK
  Date: Thu, 16 Feb 2006 22:12:27 GMT
  Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
  Cache-Control: no-cache
  Pragma: no-cache
  Expires: Wed, 31 Dec 1969 23:59:59 GMT
  Content-Type: text/html;charset=UTF-8
  X-Cache: MISS from proxy01.spidernet.net
  X-Cache-Lookup: MISS from proxy01.spidernet.net:83
  Proxy-Connection: close
  
  Obviously, the response is the same in both cases,
 however,
  for FireFox the
  important difference I see in Request is the one
 saying Cache-control:
  max-age=0 and also, the Keep-Alive value 300. I do
 not think
  the Keep-Alive
  value is the problem, however, the Cache-Control:
 max-age=0
  is suspicious.
  In my code I have
  response.setHeader(Cache-Control,no-cache) but
 I think
  this is different.  Does anyone have a clue what
 the
  max-age:0 is doing?
  
  Your help will be greatly appreciated.
  
  
  Thanks and regards,
  Michael
  
  -Original Message-
  From: Filip Hanik - Dev Lists
 [mailto:[EMAIL PROTECTED]
  Sent: 15 February 2006 22:16
  To: Tomcat Users List
  Subject: Re: Session Expires At Every Request
 (Tomcat5.0.28/Firefox)
  
  George Sexton wrote:
   Does the code transparently create a new
 JSessionID value then?
  
  George,
  you might wanna rethink your comments, they don't
 shine any
  light on the issue and they for sure don't state
 any facts,
  let me prove you I am right. Below is the headers
 I tracked
  with LiveHttpHeaders, as you can see, JSESSIONID
 remains
  exactly the same in the browser request when the
 switch from
  HTTP to HTTPS happens.
  This is Firefox on Fedora 4. The site works fine.
  
  This must be a browser issue, can you tell us a
 little bit
  more about what version and platform your browser
 is on.
  
  1. Request to the home - non secure
 


  http://www.tophotelchoices.com/
  GET / HTTP/1.1
  Host: www.tophotelchoices.com
  User-Agent: Mozilla/5.0 (X11; U; Linux i686;
 en-US; rv:1.8.0.1)
  Gecko/20060124 Firefox/1.5.0.1
  Accept: 
 

text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
  text/plain;q=0.8,image/png,*/*;q=0.5
  Accept-Language: en-us,en;q=0.5
  Accept-Encoding: gzip,deflate
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
  Keep-Alive: 300
  Connection: keep-alive
  Referer: http://www.tophotelchoices.com/
  
  HTTP/1.x 200 OK
  Date: Wed, 15 Feb 2006 20:08:55 GMT
  Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
  Set-Cookie:
 JSESSIONID=735009FD40D725EDAA14389409CD60FF; Path=/
  Cache-Control: no-cache
  Pragma: no-cache
  Expires: Wed, 31 Dec 1969 23:59:59 GMT
  Keep-Alive: timeout=5, max=20
  Connection: Keep-Alive
  Transfer-Encoding: chunked
  Content-Type: text/html;charset=UTF-8
  
  2. Click on the request button - switch from HTTP
 to HTTPS
 

https://www.tophotelchoices.com/bookingServlet1?hotel=ASI
  GET /bookingServlet1?hotel=ASI HTTP/1.1
  Host: www.tophotelchoices.com:443
  User-Agent: Mozilla/5.0 (X11; U; Linux i686;
 en-US; rv:1.8.0.1)
  Gecko/20060124 Firefox/1.5.0.1
  Accept: 
 

text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
  text/plain;q=0.8,image/png,*/*;q=0.5
  Accept-Language:

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-16 Thread Michael Andreas Omerou 
More or less this what I think as well! That Cache-control: max-age=0 is
applied to cookies too.  However the cookies in Firefox seem to have the
correct expiration date.

Michael

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: 17 February 2006 06:03
To: users@tomcat.apache.org
Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Michael Andreas Omerou [EMAIL PROTECTED] wrote in 
message news:[EMAIL PROTECTED]
 Dear all,

 Thanks for your replies to my problem.  However, I think the 
 discussion has been diverted into a debate totally 
irrelevant to the 
 issue.


Not that I'm all that interested, but just to push this along, 
what are the Cookie properties in FireFox after you request a page?

Personally, I'm betting that FireFox is probably applying your 
cache-control/max-age headers to the Cookies as well as to the 
page itself.

 As far as Chuck's question whether this could be related to 
the popup, 
 this is not the case as the problem happens on other pages too, even 
 on index.jsp (first page)

 Regarding Filip's email and monitoring HTTP Headers I am impressed 
 that it seems to work for you.  I run FireFox on Windows XP Pro SP2 
 and what happens is that when a page finishes loading, the session 
 expires on the server.
 When the user/browser requests another page the correct 
session id is 
 sent from the browser but the server detects that this 
session id sent 
 is no more valid (expired) and so we have a timeout.  However, this 
 behaviour, only
 occurs with FireFox.   I tried it from another PC with XP 
Pro SP2 too but
 the problem is the same.  With IE, NetScape and Opera all is ok.



 I want to emphasize that this behaviour does not happen only when 
 switching from SSL to non-SSL or vice versa.  Even if I try 
to access 
 pages such as the About Us or the Contact Us the session expires 
 again.  However, in that case the problem is not visible 
to the user 
 since those pages do not contain any session specific data so even 
 with a new session it is ok.
 Try
 the following though and you will see what I mean.  On 
 tophotelchoices.com do a search for a hotel.  Let the results be 
 displayed and then, go to the About Us page.  Then, click your 
 browser's back button and instead of going back to the 
search results 
 you get a timeout (if you get search results it will be from 
browser's 
 cache, do a reload and you will get timeout).

 Monitoring the HTTP headers for both IE and Firefox using 
HttpAnalyzer 
 for IE and LiveHttpHeaders for Firefox gives the following:
 1) IE

 (Request-Line):GET http://www.tophotelchoices.com/ HTTP/1.1
 Accept:*/*
 Accept-Language:en-gb
 Accept-Encoding:gzip, deflate
 User-Agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
 .NET CLR 1.1.4322; InfoPath.1) Host:www.tophotelchoices.com 
 Proxy-Connection:Keep-Alive Pragma:no-cache 
 Cookie:JSESSIONID=6F187E9E698F5D81A09DF6AD0D25115D

 (Status-Line):HTTP/1.0 200 OK
 Date:Thu, 16 Feb 2006 22:09:18 GMT
 Server:Apache/1.3.33 (Unix) mod_jk/1.2.15 Cache-Control:no-cache 
 Pragma:no-cache Expires:Wed, 31 Dec 1969 23:59:59 GMT
 Content-Type:text/html;charset=UTF-8
 X-Cache:MISS from proxy01.spidernet.net X-Cache-Lookup:MISS from 
 proxy01.spidernet.net:83 Proxy-Connection:close

 2) FIREFOX:
 GET http://www.tophotelchoices.com/index.jsp HTTP/1.1
 Host: www.tophotelchoices.com
 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; 
rv:1.7.12)
 Gecko/20050919 Firefox/1.0.7
 Accept:
 
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/pl
 ain;q=
 0.8,image/png,*/*;q=0.5
 Accept-Language: en-gb,en;q=0.5
 Accept-Encoding: gzip,deflate
 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive: 300
 Proxy-Connection: keep-alive
 Referer: http://www.tophotelchoices.com/timeout.jsp
 Cookie: JSESSIONID=3849A82D2F9B6991FE41073D771D1358
 Cache-Control: max-age=0

 HTTP/1.x 200 OK
 Date: Thu, 16 Feb 2006 22:12:27 GMT
 Server: Apache/1.3.33 (Unix) mod_jk/1.2.15
 Cache-Control: no-cache
 Pragma: no-cache
 Expires: Wed, 31 Dec 1969 23:59:59 GMT
 Content-Type: text/html;charset=UTF-8
 X-Cache: MISS from proxy01.spidernet.net
 X-Cache-Lookup: MISS from proxy01.spidernet.net:83
 Proxy-Connection: close

 Obviously, the response is the same in both cases, however, for 
 FireFox the important difference I see in Request is the one saying 
 Cache-control:
 max-age=0 and also, the Keep-Alive value 300. I do not think the 
 Keep-Alive value is the problem, however, the Cache-Control: 
max-age=0 
 is suspicious.
 In my code I have 
response.setHeader(Cache-Control,no-cache) but I 
 think this is different.  Does anyone have a clue what the max-age:0 
 is doing?

 Your help will be greatly appreciated.


 Thanks and regards,
 Michael

-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 22:16
To: Tomcat Users List
Subject: Re: Session Expires At Every Request (Tomcat5.0.28/Firefox

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-16 Thread Michael Andreas Omerou 
Thanks for the suggestion George.

I don't think is the proxy because IE and other browsers work with the same
proxy so I don't see why FireFox should not.  I will try your suggestion
though and let you know the outcome.

As far as other suggestions, no. 1 is particularly interesting and will try
it, as well as no.2.  For your third suggestion I explained to you why I am
doing it.

As far as the X-Cache: MISS, etc. these appear with IE as well but IE works
so it can't be the problem.

Michael

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: 17 February 2006 05:22
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; 'Joey Geiger'; [EMAIL PROTECTED]
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Since I regularly use Firefox and sessions I'm pretty sure 
that there is really nothing unique to that combination that 
is causing the problem. It could be the proxy server below is 
causing the issue. The obvious thing to do would be to try 
from a different network without a proxy server and see if 
your issue clears up.

I would also recommend that you do a little cleanup on your 
HTML pages and see if there is some effect on the issue. The 
specific things I would fix in your HTML are:

1) No DocType, causing the page to render in Quirks mode. FYI, this
will cause differences in the box model which will result in 
IE 6.0 and FireFox/Mozilla displaying pages very differently.

2) No Content type/charset meta in the header.

3) You have a duplicate HEAD block in the bottom of your page.

Your reference to the cache-control entry:


 Cache-Control: max-age=0

Doesn't appear in my browser. I would suspect that its being 
added by your proxy server.

 X-Cache: MISS from proxy01.spidernet.net
 X-Cache-Lookup: MISS from proxy01.spidernet.net:83

I would also say that if you're going to use the addHeader() 
to put in cache/pragma entries that you should not use the META tags.





George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

 -Original Message-
 From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 16, 2006 3:38 PM
 To: 'Tomcat Users List'
 Cc: [EMAIL PROTECTED]; 'George Sexton'; 'Joey Geiger'; 
 [EMAIL PROTECTED]
 Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)
 
 Dear all,
 
 Thanks for your replies to my problem.  However, I think the 
 discussion has been diverted into a debate totally 
irrelevant to the 
 issue.
 
 As far as Chuck's question whether this could be related to 
the popup, 
 this is not the case as the problem happens on other pages too, even 
 on index.jsp (first page)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Session Problems with Firefox

2006-02-15 Thread Michael Andreas Omerou 
Hello,

I have some problems with session management when our application runsin
Firefox.

Basically, what happens is that after I set in the session some
attributes/beans which are needed down the application, I check in all JSPs
and servlets that an old session is still there by using 
if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that the session is
re-initialised whenever the client/browser requests a new page.  I checked
this by printing the session id in the log on each page and with IE it does
not change, while with Firefox it changes.  

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Problems with Firefox

2006-02-15 Thread Michael Andreas Omerou 
Further to my below email I have put in some code to check the HTTP headers
in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of FireFox but not
in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our 
application runsin Firefox.

Basically, what happens is that after I set in the session 
some attributes/beans which are needed down the application, I 
check in all JSPs and servlets that an old session is still 
there by using 
   if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that 
the session is re-initialised whenever the client/browser 
requests a new page.  I checked this by printing the session 
id in the log on each page and with IE it does not change, 
while with Firefox it changes.  

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
 Anybody has an idea what could be causing what I describe in the below two
emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the 
HTTP headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
SV1; .NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of 
FireFox but not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I 
check in all 
JSPs and servlets that an old session is still there by using
  if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that 
the session 
is re-initialised whenever the client/browser requests a new page.  I 
checked this by printing the session id in the log on each page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason that at then
end of loading each JSP firefox expires my session.  I use some meta tags
(META HTTP-EQUIV=Cache-Control CONTENT=No-Cache, META
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values using
response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in 
the below two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of 
FireFox but 
not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
check in all
JSPs and servlets that an old session is still there by using
 if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that
the session
is re-initialised whenever the client/browser requests a new 
page.  I 
checked this by printing the session id in the log on each page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
It is 30 minutes.  If I do request.getSession().getMaxInactiveInterval() I
get 1800 (seconds I guess) which is the correct value for 30 minutes. 

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox 
would not be the one that expires your session, Tomcat would. 
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason 
that at then end of loading each JSP firefox expires my 
session.  I use some meta tags (META 
HTTP-EQUIV=Cache-Control CONTENT=No-Cache, META 
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values 
using response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in 
the below 
two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; 
rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
FireFox but
not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
check in all
JSPs and servlets that an old session is still there by using
if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that
the session
is re-initialised whenever the client/browser requests a new
page.  I
checked this by printing the session id in the log on each page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
In principle,  one could try the below (a stand-alone jsp) which resides in
my application with a timeout of 30 minutes:

[EMAIL PROTECTED] import=java.util.Enumeration,java.util.Date
contentType=text/html%
[EMAIL PROTECTED] pageEncoding=UTF-8%
html
headtitleJSP Page/title/head
body
%

  Enumeration reqHeaderNames = request.getHeaderNames();
  String curHeaderName;
while (reqHeaderNames.hasMoreElements()){
curHeaderName=(String) reqHeaderNames.nextElement();
System.out.println(curHeaderName + :  +
request.getHeader(curHeaderName));
}
  
  System.out.println(TestFirefox.jsp Session ID Value: +
request.getSession(false).getId());
  
%
TEST FIREFOX LOADED

/body
/html


The above creates a new session wheneven reloaded in Firefox while in IE it
keeps the same.

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 17:34
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

It is 30 minutes.  If I do 
request.getSession().getMaxInactiveInterval() I get 1800 
(seconds I guess) which is the correct value for 30 minutes. 

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox would not 
be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason that at 
then end of loading each JSP firefox expires my session.  I use some 
meta tags (META HTTP-EQUIV=Cache-Control 
CONTENT=No-Cache, META 
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in
the below
two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
FireFox but
not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
check in all
JSPs and servlets that an old session is still there by using
   if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that
the session
is re-initialised whenever the client/browser requests a new
page.  I
checked this by printing the session id in the log on each 
page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
Not at the stage that this problem occurs.  SSL is used further on when the
user logs in to make a payment but the SSL pages are never reached with
FireFox because of the early timeout.  With IE all is ok, including SSL
connections. 

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 17:43
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you using SSL connection ?

-Message d'origine-
De :
[EMAIL PROTECTED]
pache.org
[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
tomcat.ap
ache.org]De la part de Michael Andreas Omerou Envoye : 
mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


It is 30 minutes.  If I do 
request.getSession().getMaxInactiveInterval() I get 1800 
(seconds I guess) which is the correct value for 30 minutes. 

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox would not 
be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some reason that at 
then end of loading each JSP firefox expires my session.  I use some 
meta tags (META HTTP-EQUIV=Cache-Control 
CONTENT=No-Cache, META 
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in
the below
two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
FireFox but
not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
check in all
JSPs and servlets that an old session is still there by using
   if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox, it seems that
the session
is re-initialised whenever the client/browser requests a new
page.  I
checked this by printing the session id in the log on each 
page and 
with IE it does not change, while with Firefox it changes.

I checked my firefox settings for cookies and all look ok.

Anybody has a clue of what I might be doing wrong?

Regards,
Michael



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
I tried with NetScape and Opera to see what happens.  

For NetScape the first time I tried it was ok up to the stage that I
switched to SSL.  At that step, I lost my session.  After trying several
times again I noticed NetScape was ok.

With Opera all works fine, like with IE, from the beginning.

So major problem is still FireFox and it must be something that it sends (or
not sends) back to Tomcat that causes session expiration.

Thanks for your assistance.

Michael

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 17:48
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Not at the stage that this problem occurs.  SSL is used 
further on when the user logs in to make a payment but the SSL 
pages are never reached with FireFox because of the early 
timeout.  With IE all is ok, including SSL connections. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:43
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you using SSL connection ?

-Message d'origine-
De :
[EMAIL PROTECTED]
pache.org
[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
tomcat.ap
ache.org]De la part de Michael Andreas Omerou Envoye : 
mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


It is 30 minutes.  If I do
request.getSession().getMaxInactiveInterval() I get 1800 (seconds I 
guess) which is the correct value for 30 minutes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox 
would not 
be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some 
reason that at 
then end of loading each JSP firefox expires my session.  I use some 
meta tags (META HTTP-EQUIV=Cache-Control
CONTENT=No-Cache, META
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in
the below
two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check 
the HTTP 
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 
5.1; SV1; 
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
FireFox but
not in the case of IE could be the cause of my problems.

Michael



-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 11:27
To: users@tomcat.apache.org
Subject: Session Problems with Firefox

Hello,

I have some problems with session management when our application 
runsin Firefox.

Basically, what happens is that after I set in the session some 
attributes/beans which are needed down the application, I
check in all
JSPs and servlets that an old session is still there by using
  if (request.getSession(false)==null){
 
response.sendRedirect(response.encodeRedirectURL(timeout.jsp));

}

With IE all works fine, however with Firefox

RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

2006-02-15 Thread Michael Andreas Omerou 
As the problem occurs with a live site, you can see it yourself at
www.tophotelchoices.com.  Do a search for any hotel.   You will see the
results.  By the time the results page is loaded your session has expired
but you do not know.  Click on the Book or Request button of any hotel
and you will see the Timeout page.

Remember that the above only happens with FireFox.

I will greatly appreciate your help.

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED] 
Sent: 15 February 2006 19:45
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

I tried with NetScape and Opera to see what happens.  

For NetScape the first time I tried it was ok up to the stage 
that I switched to SSL.  At that step, I lost my session.  
After trying several times again I noticed NetScape was ok.

With Opera all works fine, like with IE, from the beginning.

So major problem is still FireFox and it must be something 
that it sends (or not sends) back to Tomcat that causes 
session expiration.

Thanks for your assistance.

Michael

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:48
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Not at the stage that this problem occurs.  SSL is used 
further on when 
the user logs in to make a payment but the SSL pages are 
never reached 
with FireFox because of the early timeout.  With IE all is ok, 
including SSL connections.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:43
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

Are you using SSL connection ?

-Message d'origine-
De :
[EMAIL PROTECTED]
pache.org
[mailto:users-return-140612-alexandre.tastet=fr.fortisbank.com@
tomcat.ap
ache.org]De la part de Michael Andreas Omerou Envoye : 
mercredi 15 fevrier 2006 16:34 A : 'Tomcat Users List'
Objet : RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


It is 30 minutes.  If I do
request.getSession().getMaxInactiveInterval() I get 1800 (seconds I
guess) which is the correct value for 30 minutes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:25
To: Tomcat Users List
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)

The META tags should not have an effect on cookies. Firefox
would not
be the one that expires your session, Tomcat would.
Do you have a session timeout specified in your application?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:19 AM
To: 'Tomcat Users List'
Subject: RE: Session Expires At Every Request (Tomcat5.0.28/Firefox)


Hi Earnie,

Cookies are allowed at the browser.  It seems for some
reason that at
then end of loading each JSP firefox expires my session.  I 
use some 
meta tags (META HTTP-EQUIV=Cache-Control
CONTENT=No-Cache, META
HTTP-EQUIV=Pragma CONTENT=No-Cache, META HTTP-EQUIV=Expires
CONTENT=-1) and also set the corresponding header values using 
response.setHeader but even if I remove them nothing changes.

Michael

-Original Message-
From: Earnie Dyke [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 17:10
To: Tomcat Users List
Subject: RE: Session Expires At Every Request 
(Tomcat5.0.28/Firefox)

Are you blocking cookies at the browser?

Earnie!

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 10:06 AM
To: 'Tomcat Users List'
Subject: Session Expires At Every Request (Tomcat5.0.28/Firefox)


 Anybody has an idea what could be causing what I describe in
the below
two emails?

-Original Message-
From: Michael Andreas Omerou [mailto:[EMAIL PROTECTED]
Sent: 15 February 2006 13:10
To: 'Tomcat Users List'
Subject: RE: Session Problems with Firefox

Further to my below email I have put in some code to check
the HTTP
headers in each case (IE and FireFox).

These are:

IE
accept: */*
accept-language: en-gb
accept-encoding: gzip, deflate
user-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
5.1; SV1;
.NET CLR 1.1.4322; InfoPath.1)
host: localhost
connection: Keep-Alive
cookie: JSESSIONID=D79835F3D70ADD58F4770DD15B463320

FireFox
host: localhost
user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.12)
Gecko/20050919 Firefox/1.0.7
accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,
text/plain;q=
0.8,image/png,*/*;q=0.5
accept-language: en-gb,en;q=0.5
accept-encoding: gzip,deflate
accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
keep-alive: 300
connection: keep-alive
cookie: JSESSIONID=A3893195B065989E5B03BC8681E4D0D6
cache-control: max-age=0


I wonder whether the keep-alive which exists in the case of
FireFox but
not in the case of IE could be the cause of my problems

RE: Problem with mod_jk Connector

2005-12-14 Thread Michael Andreas Omerou 
Hi Martin,

Thanks for your message and I apologise for the late reply but I have been
so busy with so many other things.

Before I proceed with using forwardAll as you suggested I would like to ask
you whether using forwardAll will still allow me to use JkUnmount.

Thanks,
Michael

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: 11 December 2005 16:11
To: [EMAIL PROTECTED]
Cc: Tomcat Users List
Subject: Re: Problem with mod_jk Connector

Straight from the doc available at
http://tomcat.apache.org/connectors-doc/config/apache.html

forwardAll=true
in your httpd.conf forwards ALL requests to tomcat


JkUnMount takes precedence over JkMount directives, meaning 
that the JK will first look for unmount and then for mount 
directives. The following example will block all .gif files.

  # do not send requests ending with .gif to worker1
  JkUnMount /*.gif worker1
  # The .gif files will not be mounted cause JkUnMount takes
  # precedence over JkMount directive
  JkMount /servlet/*.gif worker1so in effect your JkUnmount 
statement is blocking access to the parameter following 
JkUnmount commandMartin-


- Original Message - 
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: 'Tomcat Users List' users@tomcat.apache.org; 'Martin Gainty' 
[EMAIL PROTECTED]
Sent: Sunday, December 11, 2005 3:57 AM
Subject: RE: Problem with mod_jk Connector


 Hi Martin,

 Below is my entire workers.properties file:

 workers.tomcat_home=/usr/local/jakarta/jakarta-tomcat
 workers.java_home=/usr/local/j2sdk
 ps=/
 worker.list=ajp13
 worker.ajp13.type=ajp13
 worker.ajp13.host=localhost
 worker.ajp13.port=8009
 worker.ajp13.lbfactor=50
 worker.ajp13.cachesize=10
 worker.ajp13.cache_timeout=600
 worker.ajp13.socket_keepalive=1
 worker.ajp13.socket_timeout=300

 I have set JKLogLevel to info but although the problem 
occurs nothing goes
 there.  In fact even for requests forwarded from Apache to 
Tomcat there 
 are
 no entries in mod_jk.log.

 Regarding forwardAll I am not aware of this option, where does it go?
 Please note that eventually I need to have the JKUnmount in 
my httpd.conf.

 Thanks,
 Michael



-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 10 December 2005 23:02
To: [EMAIL PROTECTED]
Cc: 'Tomcat Users List'
Subject: Re: Problem with mod_jk Connector

what this says is that all requests goto ajp13 worker I will
need to see worker.properties file and the value of forwardAll
set JkLogLevel info

Martin-
- Original Message -
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: 'Tomcat Users List' users@tomcat.apache.org; 
'Martin Gainty'
[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 2:33 PM
Subject: RE: Problem with mod_jk Connector


 Hi Martin,

 Below is the extract from my httpd.conf:
 LoadModule jk_module
modules/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so
 JkWorkersFile /usr/local/etc/httpd/conf/workers.properties
 JkLogFile /usr/local/etc/httpd/logs/mod_jk.log
 JkLogLevel error
 JkMount /* ajp13

 The idea is that all requests (jsp, servlets, images, etc.)
are forwarded
 from Apache to Tomcat and this works fine with mod_jk
version 1.2.5.  When
 I
 upgraded to 1.2.15 though the forwards still work but only
if there are no
 URL parameters.  This is what I cannot understand: if there are URL
 parameters then it looks as if Apache tried to serve the
request instead
 of
 forwarding to Tomcat.

 Any help will be much appreciated.

 Thanks in advance,
 Michael


-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 10 December 2005 17:50
To: [EMAIL PROTECTED]
Cc: users@tomcat.apache.org
Subject: Re: Problem with mod_jk Connector

Michael-
in your httpd.conf we need to see JKMount statement for
handling *.jsp pages see
http://tomcat.apache.org/tomcat-4.1-doc/config/jk.html
e.g.
For example the following directives will send all requests
ending in .jsp or with /servlet as the second path componenet
to the ajp13 worker, but jsp requests to files located in
/otherworker will go to remoteworker.

   JkMount /*.jsp ajp13
   JkMount /*/servlet/ ajp13
   JkMount /otherworker/*.jsp remoteworker
Martin-- Original Message -
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Saturday, December 10, 2005 10:25 AM
Subject: Problem with mod_jk Connector


 Hello,

 I have a Solaris server where I use Apache and Tomcat and I
connect them
 using mod_jk.  So far I was using mod_jk 1.2.5 and all
requests to Apache
 were forwarded to Tomcat.  Then, I needed to host some
things under Apache
 (basically web statistics software, webmail, etc.).  So I
thought of using
 JkUnmount to do this.

 JkUnmoun is not supported from mod_jk 1.2.5 so I installed
the latest
 version 1.2.15.  Now JkUnmount works but I have another problem.

 If a url which is meant to be sent to Tomcat contains URL
parameters, e.g.
 something like ./hotelDetails.jsp?hotelCode=AMY, then
the request

RE: Problem with mod_jk Connector

2005-12-11 Thread Michael Andreas Omerou 
Hi Martin,

Below is my entire workers.properties file:

workers.tomcat_home=/usr/local/jakarta/jakarta-tomcat
workers.java_home=/usr/local/j2sdk
ps=/
worker.list=ajp13
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
worker.ajp13.lbfactor=50
worker.ajp13.cachesize=10
worker.ajp13.cache_timeout=600
worker.ajp13.socket_keepalive=1
worker.ajp13.socket_timeout=300

I have set JKLogLevel to info but although the problem occurs nothing goes
there.  In fact even for requests forwarded from Apache to Tomcat there are
no entries in mod_jk.log.

Regarding forwardAll I am not aware of this option, where does it go?
Please note that eventually I need to have the JKUnmount in my httpd.conf.

Thanks,
Michael

 

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: 10 December 2005 23:02
To: [EMAIL PROTECTED]
Cc: 'Tomcat Users List'
Subject: Re: Problem with mod_jk Connector

what this says is that all requests goto ajp13 worker I will 
need to see worker.properties file and the value of forwardAll 
set JkLogLevel info

Martin-
- Original Message -
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: 'Tomcat Users List' users@tomcat.apache.org; 'Martin Gainty' 
[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 2:33 PM
Subject: RE: Problem with mod_jk Connector


 Hi Martin,

 Below is the extract from my httpd.conf:
 LoadModule jk_module 
modules/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so
 JkWorkersFile /usr/local/etc/httpd/conf/workers.properties
 JkLogFile /usr/local/etc/httpd/logs/mod_jk.log
 JkLogLevel error
 JkMount /* ajp13

 The idea is that all requests (jsp, servlets, images, etc.) 
are forwarded
 from Apache to Tomcat and this works fine with mod_jk 
version 1.2.5.  When 
 I
 upgraded to 1.2.15 though the forwards still work but only 
if there are no
 URL parameters.  This is what I cannot understand: if there are URL
 parameters then it looks as if Apache tried to serve the 
request instead 
 of
 forwarding to Tomcat.

 Any help will be much appreciated.

 Thanks in advance,
 Michael


-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 10 December 2005 17:50
To: [EMAIL PROTECTED]
Cc: users@tomcat.apache.org
Subject: Re: Problem with mod_jk Connector

Michael-
in your httpd.conf we need to see JKMount statement for
handling *.jsp pages see
http://tomcat.apache.org/tomcat-4.1-doc/config/jk.html
e.g.
For example the following directives will send all requests
ending in .jsp or with /servlet as the second path componenet
to the ajp13 worker, but jsp requests to files located in
/otherworker will go to remoteworker.

   JkMount /*.jsp ajp13
   JkMount /*/servlet/ ajp13
   JkMount /otherworker/*.jsp remoteworker
Martin-- Original Message -
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Saturday, December 10, 2005 10:25 AM
Subject: Problem with mod_jk Connector


 Hello,

 I have a Solaris server where I use Apache and Tomcat and I
connect them
 using mod_jk.  So far I was using mod_jk 1.2.5 and all
requests to Apache
 were forwarded to Tomcat.  Then, I needed to host some
things under Apache
 (basically web statistics software, webmail, etc.).  So I
thought of using
 JkUnmount to do this.

 JkUnmoun is not supported from mod_jk 1.2.5 so I installed 
the latest
 version 1.2.15.  Now JkUnmount works but I have another problem.

 If a url which is meant to be sent to Tomcat contains URL
parameters, e.g.
 something like ./hotelDetails.jsp?hotelCode=AMY, then
the request is
 not
 forwarded from Apache/Mod_jk.

 I checked everywhere for solutions to this but could not find any.

 Your help willl be much appreciated.

 Rgds,
 Michael


 
-
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with mod_jk Connector

2005-12-10 Thread Michael Andreas Omerou 
Hello,

I have a Solaris server where I use Apache and Tomcat and I connect them
using mod_jk.  So far I was using mod_jk 1.2.5 and all requests to Apache
were forwarded to Tomcat.  Then, I needed to host some things under Apache
(basically web statistics software, webmail, etc.).  So I thought of using
JkUnmount to do this.

JkUnmoun is not supported from mod_jk 1.2.5 so I installed the latest
version 1.2.15.  Now JkUnmount works but I have another problem.

If a url which is meant to be sent to Tomcat contains URL parameters, e.g.
something like ./hotelDetails.jsp?hotelCode=AMY, then the request is not
forwarded from Apache/Mod_jk.

I checked everywhere for solutions to this but could not find any.

Your help willl be much appreciated.

Rgds,
Michael


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problem with mod_jk Connector

2005-12-10 Thread Michael Andreas Omerou 
Hi Martin,

Below is the extract from my httpd.conf:
LoadModule jk_module modules/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so
JkWorkersFile /usr/local/etc/httpd/conf/workers.properties
JkLogFile /usr/local/etc/httpd/logs/mod_jk.log
JkLogLevel error
JkMount /* ajp13

The idea is that all requests (jsp, servlets, images, etc.) are forwarded
from Apache to Tomcat and this works fine with mod_jk version 1.2.5.  When I
upgraded to 1.2.15 though the forwards still work but only if there are no
URL parameters.  This is what I cannot understand: if there are URL
parameters then it looks as if Apache tried to serve the request instead of
forwarding to Tomcat.

Any help will be much appreciated.

Thanks in advance,
Michael
 

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: 10 December 2005 17:50
To: [EMAIL PROTECTED]
Cc: users@tomcat.apache.org
Subject: Re: Problem with mod_jk Connector

Michael-
in your httpd.conf we need to see JKMount statement for 
handling *.jsp pages see 
http://tomcat.apache.org/tomcat-4.1-doc/config/jk.html
e.g.
For example the following directives will send all requests 
ending in .jsp or with /servlet as the second path componenet 
to the ajp13 worker, but jsp requests to files located in 
/otherworker will go to remoteworker.

   JkMount /*.jsp ajp13
   JkMount /*/servlet/ ajp13
   JkMount /otherworker/*.jsp remoteworker
Martin-- Original Message -
From: Michael Andreas Omerou [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Saturday, December 10, 2005 10:25 AM
Subject: Problem with mod_jk Connector


 Hello,

 I have a Solaris server where I use Apache and Tomcat and I 
connect them
 using mod_jk.  So far I was using mod_jk 1.2.5 and all 
requests to Apache
 were forwarded to Tomcat.  Then, I needed to host some 
things under Apache
 (basically web statistics software, webmail, etc.).  So I 
thought of using
 JkUnmount to do this.

 JkUnmoun is not supported from mod_jk 1.2.5 so I installed the latest
 version 1.2.15.  Now JkUnmount works but I have another problem.

 If a url which is meant to be sent to Tomcat contains URL 
parameters, e.g.
 something like ./hotelDetails.jsp?hotelCode=AMY, then 
the request is 
 not
 forwarded from Apache/Mod_jk.

 I checked everywhere for solutions to this but could not find any.

 Your help willl be much appreciated.

 Rgds,
 Michael


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]