Bocalinda wrote:
This works perfectly as I expected. However, the problem I have is that some
images or links on my webapp are specified relatively.
For example <img href="image.gif">, which results in errors because the
image cannot be found on the root of my server, which is logical.
Maybe just a note before you go make all kinds of changes.
With an <img> tag like above, it is not so that the server will look in
the DocumentRoot.
You have to look at it the other way around.
The browser, when it sees this tag in the current page, is going to
"compose" a URL to retrieve it, on the base of :
- the URL at which it retrieved the current page (the one that contains
the <img> tag
- removing the last component (iow the name of the page itself)
- then substituting the "image.gif" part
In other words, if the current page was retrieved at :
http://yourserver.com/SEDO/subdir/mypage.html
and that page contains the tag above, then the browser will retrieve the
image at
http://yourserver.com/SEDO/subdir/image.gif
The server has nothing to do with it, it just tries to deliver what is
requested by the browser.
Now, for your static elements like images, you have two choices :
- either you let things go as above, these requests will be forwarded to
Tomcat, will be balanced, and it means your images should be at the
corresponding locations in your Tomcat's
- or you do something at the Apache level that will prevent these URLs
to be passed to Tomcat, and you serve them locally at the Apache level.
In other words you exclude links ending in ".gif", ".jpg", ".xxx" from
the proxying.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
