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 display.

The actual source from that page <view source> shows this:

<td valign="top" class="body12"><img src="images/bg_hdr_logo.gif" width="254" height="132" 
border="0"></td>


So, looking at the page that DOES display correctly I see this for the image properties:

localhost:8080/images/bg_hdr_logo.gif

It looks like both resolve to the /images folder correctly in the URL but does Apache pass the /images/ url to Tomcat?

In this case, the *only* reason I am using Apache as the front end is so that the URL can be "friendly". That is, have it run through port 80 and served up with the other web apps that Apache is running. Apache has no other role except to "pass through" the traffic to Tomcat. Apache will serve no content at all. That is it. The site, run directly to/through Tomcat is *perfect*. No problems with URL, images, anything. I just want to access the app, located on the same hardware and through the same IP as the Apache app like this:

MyDomain/MyAPP

If there is another way to have Tomcat serve the app at port 80 at the same IP address as Apache, I'd be happy to entertain it. Using AJP seemed the right way to do it.

I am going to look into Andre's suggestion to use:

<Location /MyApp>
 SetHandler jakarta-servlet
</Location>

and see what happens with that option.  I'll post back.

Pete

Christopher Schultz wrote:
-----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 correct root.

What do the URLs look like in the page itself?  Like in the <img
src="..." /> HTML elements. Is the URL is wrong, it's not going to work.

Also, if you are using Apache httpd to serve static content, URLs
containing the ";jsessionid=123456789" parameter aren't interpreted
correctly by Apache httpd and you should add "JkStripSession On" to your
configuration. This will allow Apache to properly serve static images
that include this jsessionid parameter.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmcaT0ACgkQ9CaO5/Lv0PDT5wCfY28zvbYD/BjOb6hMzjKUX81W
iFYAoIz62/NzUiYv77lcbZG7FWECgOJ1
=1YWc
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


Reply via email to