This isn’t affecting my app, but I’d like to know the reason why I’m
seeing this. In my layout, the following code
<%= image_tag "front.jpg", :size =>"760x175" %>
generates
<img alt="Front" height="175" src="/images/front.jpg?1122106054"
width=“760” />
Where is the parameter in the image src URL coming from, and why is it
there? I looked at the image tag source, and didn’t see anything
obvious. I don’t think it’s an articfact of my browser, but I’m really
not sure. I also see a similar weird parameter on my generated style
links.
Thanks
Jim
The answer is in the following write up
http://hypsometry.com/blog/on-browser-caching-asset-timestamping-and-rails
I don’t like it. Though the URL’s are internal to the page source,
they’re ugly and as pointed out, this appears to break caching as per
the W3C spec. It seems I should be able to get rid of it by setting
ENV[“RAILS_ASSET_ID”] to a zero length string . . .
Jim Frohnhofer wrote:
This isn’t affecting my app, but I’d like to know the reason why I’m
seeing this. In my layout, the following code
<%= image_tag "front.jpg", :size =>"760x175" %>
generates
<img alt="Front" height="175" src="/images/front.jpg?1122106054"
width=“760” />
Where is the parameter in the image src URL coming from, and why is it
there? I looked at the image tag source, and didn’t see anything
obvious. I don’t think it’s an articfact of my browser, but I’m really
not sure. I also see a similar weird parameter on my generated style
links.
Thanks
Jim
And my last complaint is that this makes the api documentation wrong.
Jim Frohnhofer wrote:
The answer is in the following write up
http://hypsometry.com/blog/on-browser-caching-asset-timestamping-and-rails
Jim Frohnhofer wrote:
This isn’t affecting my app, but I’d like to know the reason why I’m
seeing this. In my layout, the following code
<%= image_tag "front.jpg", :size =>"760x175" %>
generates
<img alt="Front" height="175" src="/images/front.jpg?1122106054"
width=“760” />