Our team ran into that and what we did was that we had the images served by
the
web server (no JRun) and the rest was served by the JRun server.
Specifically,
we have our application configured with an application mapping other than
"/",
in our case "/whk". The JSP and HTML refer to images with a direct path,
such
as "/images/myimage.gif" rather than "/whk/images/myimage.gif" and what this
does is cause the image to be served via the web server itself rather than
by
JRun. It works for us, anyway...
Mark
-----Original Message-----
From: Dave Rader [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 10:49 AM
To: JRun-Talk
Subject: Caching images (HTTP 304 response)
Hello,
I've noticed that JRun does not seem to support browser caching of images
(and other mostly static include files, like stylesheets, javascript, etc).
The full image is always re-downloaded, and the HTTP 304 response (file has
not changed) is never returned to the browser. This increases the traffic
our servers see, and slows down loading of each page.
Are there any configuration settings to have JRun support this caching?
Thanks,
Dave
----------------------------------------------------------------------------
--
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe:
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe'
in the body.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
