Re: AJP13 Connector and JKOptions

2009-02-20 Thread Pete Helgren
Thanks. I *will* dig deeper and experiment a bit when I get the time. I doubt that Freemarker had much impact on the final rendering and the context since it is just a templating tool, not specific to web apps. Niggle (which uses Freemarker) might have something to do with it and we had a de

Re: AJP13 Connector and JKOptions

2009-02-20 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete, On 2/20/2009 12:25 AM, Pete Helgren wrote: > Chris suggested that I use > JKMount //* but not knowing exactly how that would play when > the context was ROOT With "JkMount /context/*", a ROOT-deployed application won't work without other config

Re: AJP13 Connector and JKOptions

2009-02-20 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete, On 2/19/2009 2:46 PM, Pete Helgren wrote: > I use Freemarker (and a smaller framework called niggle) as my servlet > template engine and the only other thing I reference is a resource base > in the servlet context like this: > > >

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Pete Helgren
Thanks for your patience Andre. I appreciate your careful, step by step description. I tried a couple of things based on your information and a suggestion from Chris. I started by trying JKMount of /* to my worker and it did work, like I expected, but it also broke all the other apps that Ap

Re: AJP13 Connector and JKOptions

2009-02-19 Thread André Warnier
Pete Helgren wrote: Thanks Andre. And, I DID carefully read your original post and I had some inkling that the problem had to do with context vs the JKMount directive. I had concluded that Apache had difficulty serving the images and I figured that the JKMount reference somehow was in the mi

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Pete Helgren
Chris, Thanks I'll that that to heart and dig deeper into the application structure itself when I get the opportunity. I use Freemarker (and a smaller framework called niggle) as my servlet template engine and the only other thing I reference is a resource base in the servlet context like th

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete, On 2/19/2009 12:31 PM, Pete Helgren wrote: > My servlet uses templates that are relative to the webapps/ > folder. I don't tell the template anything more than this: > > width="254" height="115" border="0"> You should be telling it someth

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Pete Helgren
Thanks Andre. And, I DID carefully read your original post and I had some inkling that the problem had to do with context vs the JKMount directive. I had concluded that Apache had difficulty serving the images and I figured that the JKMount reference somehow was in the middle of it. Reference

Re: AJP13 Connector and JKOptions

2009-02-19 Thread André Warnier
Pete Helgren wrote: [...] Pete, I really think you should re-read my previous answer. I did a quick check on the page you indicated, using Firefox and it's LiveHttpHeaders add-on, and the result in summary is : The first link to the page, ending in /ASAAP , works fine. But subsequently, th

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Pete Helgren
Thanks Rainer. I have thought about both server name and port issues and I can't see where they might be part of the problem. I may try on my own development PC to see if I can replicate the issue. On the host server a localhost/MyApp generates the same broken link/image issue as the full my

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete, On 2/18/2009 11:35 PM, Pete Helgren wrote: > What do the URL's look like? Here is an example. If I right click and > get the properties on the "missing" image, I see this (well I'd add a > more "real" looking URL but the this mailing list has

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Rainer Jung
On 19.02.2009 15:24, Pete Helgren wrote: It does resolve to h t t p : // w w w . a c o r r e c t d o m a i n n a m e . c o m /images/bg_hdr_logo.gif I would post the real link if the firewall allowed 8080 traffic through because then you could see the difference between the 'domain reference'/im

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Pete Helgren
It is a placeholder. Unfortunately, every time I paste a link in an email and send it to the list I get it returned as undeliverable by the Apache List Software as spam. I get it back with this: There was a SMTP communication problem with the recipient's email server. Please contact your

Re: AJP13 Connector and JKOptions

2009-02-19 Thread Rainer Jung
On 19.02.2009 05:35, Pete Helgren wrote: What do the URL's look like? Here is an example. If I right click and get the properties on the "missing" image, I see this (well I'd add a more "real" looking URL but the this mailing list has rejected my last 9 attempts as spam...): MyDomain/images/bg

Re: AJP13 Connector and JKOptions

2009-02-19 Thread André Warnier
Pete Helgren wrote: What do the URL's look like? Here is an example. If I right click and get the properties on the "missing" image, I see this (well I'd add a more "real" looking URL but the this mailing list has rejected my last 9 attempts as spam...): [...] Hi again. I haven't looked in

Re: AJP13 Connector and JKOptions

2009-02-18 Thread Pete Helgren
What do the URL's look like? Here is an example. If I right click and get the properties on the "missing" image, I see this (well I'd add a more "real" looking URL but the this mailing list has rejected my last 9 attempts as spam...): MyDomain/images/bg_hdr_logo.gif and the image does NOT

Re: AJP13 Connector and JKOptions

2009-02-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete, On 2/18/2009 8:17 AM, Pete Helgren wrote: > The pages display but none of the images display and several of the > webapps links are broken. So, something isn't quite right. It is almost > as though the application links aren't relative to the c

Re: AJP13 Connector and JKOptions

2009-02-18 Thread André Warnier
János Löbb wrote: On Feb 18, 2009, at 8:17 AM, Pete Helgren wrote: Still struggling with this so I am reposting. I can't seem to find a configuration that allows the images and links to properly display. Info from prior posts: I have a Tomcat application that serves up a web app when I us

Re: AJP13 Connector and JKOptions

2009-02-18 Thread János Löbb
On Feb 18, 2009, at 8:17 AM, Pete Helgren wrote: Still struggling with this so I am reposting. I can't seem to find a configuration that allows the images and links to properly display. Info from prior posts: I have a Tomcat application that serves up a web app when I use a URL like thi

AJP13 Connector and JKOptions

2009-02-18 Thread Pete Helgren
Still struggling with this so I am reposting. I can't seem to find a configuration that allows the images and links to properly display. Info from prior posts: I have a Tomcat application that serves up a web app when I use a URL like this: http://www.mywebsite.com:8080/MyAPP Which I wante

Re: AJP13 Connector and JKOptions]

2009-02-16 Thread Pete Helgren
; To: "Tomcat Users List" Sent: Saturday, February 14, 2009 3:26 AM Subject: Re: AJP13 Connector and JKOptions Pete Helgren wrote: [...] Hi. Maybe start at the beginning and let us know : - which version of Tomcat you are running - on what kind of "box" (the OS) - with which ve

Re: AJP13 Connector and JKOptions

2009-02-14 Thread André Warnier
Pete Helgren wrote: [...] Hi. Maybe start at the beginning and let us know : - which version of Tomcat you are running - on what kind of "box" (the OS) - with which version of Apache Then, - do you have any reason to be using an Apache front-end, other than wanting to get rid of the ":8080" in y

AJP13 Connector and JKOptions

2009-02-13 Thread Pete Helgren
I have a Tomcat application that happily serves up a web app when I use a URL like this: http://www.mywebsite.com:8080/MyAPP Which I wanted to change to this: http://www.mywebsite.com/MyAPP Using Apache I added the worker.properties file and the following directives to an existing Apache ser