Re: New session PER REQUEST

2006-09-26 Thread Hassan Schroeder
On 9/25/06, Maurice Yarrow <[EMAIL PROTECTED]> wrote: So, (apropos of the issues I saw with my setup) were there multiple hosts, one or more of which required both http and https access ? This particular installation had no https requirements. If that's not a complete deal-breaker, I could pro

Re: New session PER REQUEST

2006-09-25 Thread Maurice Yarrow
Hello, again, Hassan I'd like to ask a couple of questions about your | tomcat httpd <--> mod_proxy_ajp <===> | tomcat | tomcat setup. And the reason that I'm intere

Re: New session PER REQUEST

2006-09-25 Thread Maurice Yarrow
Darren Thanks for explaining what you did. I may also take a look at your method. I like not to leave stones unturned, so to speak... But it would appear that no matter which way you do it, it will have complexity if what you are trying to connect is itself a resonably complex and real-world

Re: New session PER REQUEST

2006-09-25 Thread Maurice Yarrow
Hi Hassan Yes, thanks for sharing this point: not particularly onerous. And I would have to say that the original mechanism I used just for www.mydomain.net was not too much of a problem other that the javascript URL args (which will not in browser expand relative paths to include the scheme:d

Re: New session PER REQUEST

2006-09-25 Thread Hassan Schroeder
On 9/25/06, Maurice Yarrow <[EMAIL PROTECTED]> wrote: And, fronting with Apache 2.0, and using mod_proxy, I just had one heck of a time getting this to work right. I used httpd OK, two points -- 1) it's not clear that the OP *needs* Apache in front of Tomcat -- if not, the whole issue be

RE: New session PER REQUEST

2006-09-25 Thread Darren Hall
Thanks Maurice. I'll need to look into this. > The one difficulty I have NOT seen is losing the session ID. > I do get session ID persistence where it is permitted (across http page > transitions, across https page transitions, and across http->https page > transition) > > Maurice Yarrow The los

Re: New session PER REQUEST

2006-09-25 Thread Maurice Yarrow
Hi Hassan Maurice here. Yeah, I've been following this thread, and at this moment I'm stepping into this discussion because: My tomcat has four host elements: the primary (localhost -> tomcat/webapps) as usual, plus three development hosts: devel.mydomain.net -> tomcat/webappsDevel devel2

Re: New session PER REQUEST

2006-09-25 Thread Hassan Schroeder
On 9/25/06, Darren Hall <[EMAIL PROTECTED]> wrote: ... The client does not want to see urls with an identifier on the end of them (i.e. www.abcdomain.com/abc), yet I need the identifier to correctly send the request to the correct container in Tomcat (meaning the abc app lives under the /ab

RE: New session PER REQUEST

2006-09-25 Thread Darren Hall
> Can this behavior be accomplished with mod proxy alone (meaning I can > remove mod rewrite from the picture completely)? Could this rewrite be > causing me to lose the session between Apache and Tomcat? *ding ding ding* We have a winner! I removed the rewrite rules from my httpd-vhosts.conf fil

RE: New session PER REQUEST

2006-09-25 Thread Darren Hall
I moved my port to 8081 and I still see the same behavior. *sigh* I'm still getting no positive results. I'm now thinking this issue involves one of two things. 1) Mod proxy and the way I've configured it; or 2) the rewrite rules I do on each request to and from my domain. This is my first time us

RE: New session PER REQUEST

2006-09-25 Thread Peter Crowther
> From: Darren Hall [mailto:[EMAIL PROTECTED] > (with one change - > the connector port in the new connector element I specified > is 8080, and I > also have the default element still uncommented also using > port 8080. Will this create a conflict?) I'm a little surprised it works at all. Use

RE: New session PER REQUEST

2006-09-25 Thread Darren Hall
> In server.xml (tomcat's config file), the element > receiving proxied requests from Apache HTTPd needs > proxyName="www.mysite.com" and proxyPort="80" to properly handle cookies > and writing URLs. > > There are commented examples of this in the original server.xml file > distributed with t

Re: New session PER REQUEST

2006-09-25 Thread David Smith
No. In server.xml (tomcat's config file), the element receiving proxied requests from Apache HTTPd needs proxyName="www.mysite.com" and proxyPort="80" to properly handle cookies and writing URLs. There are commented examples of this in the original server.xml file distributed with tomcat.

Re: New session PER REQUEST

2006-09-25 Thread Pid
have you consciously decided that you're using tomcat with an http mode connector instead of an ajp connector? also, you're duplicating the proxy by doing ProxyPass /flc ... as well as RewriteCond %{REQUEST_URI} !^/flc... Darren Hall wrote: > Thanks David, > >> For using mod_proxy, have

RE: New session PER REQUEST

2006-09-25 Thread Darren Hall
Thanks David, > For using mod_proxy, have you also added proxy_name and proxy_port > attributes to the connector receiving proxied requests? Those will need > to be set so tomcat can create the session cookie correctly. I don't believe I'm setting any of these things. Correct me if I'm wrong,

Re: New session PER REQUEST

2006-09-25 Thread David Smith
For using mod_proxy, have you also added proxy_name and proxy_port attributes to the connector receiving proxied requests? Those will need to be set so tomcat can create the session cookie correctly. Additionally, you might want to be sure all your links are run through response.encodeURL( ur

RE: New session PER REQUEST

2006-09-25 Thread Peter Crowther
> From: Darren Hall [mailto:[EMAIL PROTECTED] > You are correct. When hitting Tomcat directly, the session > remains intact. > When using mod_proxy to forward requests to Apache the > session is lost. > Is this a common issue? How can I go about correcting this? I'll have to open that up to the

Re: New session PER REQUEST

2006-09-24 Thread Bob Hall
Maurice Yarrow wrote: > I'm fronting tomcat 5.0.28 with apache 2.0.59 through mod_proxy. > I am not seeing loss of session persistence: here are the values > of HttpSession.getId(), as seen in a typical succession of the > servlets, and also, one of the JSP's: > > SelectPubImgSetServlet: > this

Re: New session PER REQUEST

2006-09-23 Thread Maurice Yarrow
Hello again, Bob (Sorry, slight revision/correction to wording of previous post (below), for sake of clarity:) The line "I can't, of course, tell you why you are not seeing persistent session id's, but I believe the above shows that this is normal for my webapp." should have been written

Re: New session PER REQUEST

2006-09-23 Thread Maurice Yarrow
Hi Bob I'm fronting tomcat 5.0.28 with apache 2.0.59 through mod_proxy. I am not seeing loss of session persistence: here are the values of HttpSession.getId(), as seen in a typical succession of the servlets, and also, one of the JSP's: SelectPubImgSetServlet: thisUser.getId()=303D62BDCC86A5B

Re: New session PER REQUEST

2006-09-23 Thread Martin Gainty
Peter Crowther" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Friday, September 22, 2006 12:04 PM Subject: RE: New session PER REQUEST > From: Darren Hall [mailto:[EMAIL PROTECTED] > I'm running a webapp built on Struts 1.2.9 running in Tomcat > 5.5 and

RE: New session PER REQUEST

2006-09-22 Thread Bob Hall
--- Darren Hall <[EMAIL PROTECTED]> wrote: > Peter, > You are correct. When hitting Tomcat directly, the > session remains intact. > When using mod_proxy to forward requests to Apache > the session is lost. > Is this a common issue? How can I go about > correcting this? > > Thanks > - D I don't

RE: New session PER REQUEST

2006-09-22 Thread Darren Hall
PROTECTED] Sent: Friday, September 22, 2006 12:04 PM To: Tomcat Users List Subject: RE: New session PER REQUEST > From: Darren Hall [mailto:[EMAIL PROTECTED] > I'm running a webapp built on Struts 1.2.9 running in Tomcat > 5.5 and using > an Apache 2.2 http server. I've noticed tha

RE: New session PER REQUEST

2006-09-22 Thread Peter Crowther
> From: Darren Hall [mailto:[EMAIL PROTECTED] > I'm running a webapp built on Struts 1.2.9 running in Tomcat > 5.5 and using > an Apache 2.2 http server. I've noticed that any value I put into the > session is always removed after one request/response cycle. > In the Tomcat > Manager, I can see