how to avoid the asset path warming

24 views
Skip to first unread message

Yifan Zhai

unread,
Oct 12, 2011, 5:00:22 AM10/12/11
to rubyonra...@googlegroups.com
Started GET "/assets/products.css?body=1" for 127.0.0.1 at 2011-10-12
16:46:52 +0800
Served asset /products.css - 304 Not Modified (0ms)

Started GET "/assets/users.js?body=1" for 127.0.0.1 at 2011-10-12
16:46:52 +0800
Served asset /users.js - 304 Not Modified (0ms)

Started GET "/assets/application.js?body=1" for 127.0.0.1 at 2011-10-12
16:46:52 +0800
Served asset /application.js - 304 Not Modified (1ms)

Started GET "/assets/logo.jpg" for 127.0.0.1 at 2011-10-12 16:46:53
+0800
Served asset /logo.jpg - 304 Not Modified (0ms)


The server outputs infomation like these.
Exactly those images are in path /assets/images, while js in
/assets/javascripts, css in /assets/stylesheets. Also the browser has
loaded them correctly. I guessed that Rails has mapped them in the path
/assets since I can open the css and js in the page source. But how can
i avoid those infomation in the server?

Attachments:
http://www.ruby-forum.com/attachment/6672/Snap1.jpg


--
Posted via http://www.ruby-forum.com/.

Tim Shaffer

unread,
Oct 12, 2011, 9:57:52 AM10/12/11
to rubyonra...@googlegroups.com
Those are not warnings at all. Just normal log messages.

Your browser is requesting the js, css, and jpg files with a conditional GET. The server is returning HTTP status code 304 since the file has not been modified since the last time the browser accessed. This is just a log of that transaction.

Reply all
Reply to author
Forward
0 new messages