Thanks, Sergey. I had played with that before but didn't see how I could
use it to get rid of the version number (unless I just don't configure
that).
My problem with the versioned URL is that many of my assets (particularly
PDFs, but some images as well) are things people will want to link to
directly, and if the URLs are versioned, that could be a little weird. I
guess I could make a page to pull the latest version of each file, but I was
hoping to avoid that.
On Thu, Jul 16, 2009 at 1:51 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> Why is this an issue? The longer URLs will be cached; shorter
> (direct) URLs will not be. For some data (CSS, JavaScript) the data
> sent to the browser will be GZIP compressed. What's not to like?
>
> On Wed, Jul 15, 2009 at 3:33 PM, John Frege<john.fr...@gmail.com> wrote:
> > Hi,
> > For a while now, I've been happily including images in my pages like so:
> >
> > <img src="${context:images/blah.jpg}">
> >
> > This has worked quite well, but when I view the image in my browser, I'm
> > taken to /[project name]/assets/ctx/1.0-SNAPSHOT/images/blah.jpg. I've
> read
> > that this is to aid the browser in aggressive caching, but is there
> anyway I
> > can strip the /assets/ctx/[project version] bit out of the URLs
> regardless?
> >
> > Thanks,
> > John
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
> Director of Open Source Technology at Formos
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
