Thanks for the clarification, Bruce. The image urls in the HTML are
relative:
<img src="images/cars/mini.gif">
But the url of the page is munged. I take it that the browser knows how to
ignore the sessionid in the addressbar and can figure out from the HTTP
header that the image above resides at:
www.somedomain.com/images/cars/mini.gif
even if the url of the page on which the image appears contains the
sessionid?
http://www.somedomain.com/(54gfb5zbn.../somepage.aspx
When I look at the image properties in IE, the url lacks the session id.
However, according to PageInfo in Firefox (media tab), the url of the image
contains the sessionid.
Are there any sniffers that would show me whether images are being
downloaded or retrieved from local browser cache?
Regards
Jake
"Bruce Barker" <br******************@safeco.com> wrote in message
news:#g*************@TK2MSFTNGP14.phx.gbl...
depends. if the image url include the session id, then they only be cached
for the session. if your image urls are not munged then they are cached.
normally images are not mapped to asp.net, so the cookie munger will not
see them.
-- bruce (sqlwork.com)
"Jake" <Ja**@spamspamspam.org> wrote in message
news:eC*************@TK2MSFTNGP14.phx.gbl... Does cookieless session state (with the sessionid embedded into the url)
interfere with the browser's retrieval of cached images from one session
to
the next? Does the sessionid embedded into the url effectively limit
client-side image caching to the lifetime of the session?
Thanks
Jake