Ruby on Rails: why do i get message for javascript and css after rails s?

rails s=>

Started GET "/assets/application.css?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /application.css - 304 Not Modified (0ms)


Started GET "/assets/home.css?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /home.css - 304 Not Modified (0ms)


Started GET "/assets/jquery_ujs.js?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /jquery_ujs.js - 304 Not Modified (0ms)


Started GET "/assets/jquery.js?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /jquery.js - 304 Not Modified (0ms)


Started GET "/assets/home.js?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /home开发者_开发知识库.js - 304 Not Modified (0ms)


Started GET "/assets/application.js?body=1" for 127.0.0.1 at 2011-10-11 03:37:03 -0900
Served asset /application.js - 304 Not Modified (0ms)

I get these message every time when page reloads.

How can i get rid of this message?

---

As DGM indicated, I was able to suppress most of these messages via modification to the development.rb file, specifically changing:

config.assets.debug = true

to

config.assets.debug = false

---

In development mode, it does not cache javascript or css, but rather reloads it on every call so you can see changes made.

You could either run another environment:

RAILS_ENV=production rails s

or set the config line in config/environments/development.rb

config.action_controller.perform_caching = true

---

Many times, I open another terminal window in order to control what's displayed with a command like the following:

tail -n 99 -f log/development.log| grep -e "^$" -v --line-buffered | grep -v "304 Not Modified"

That way, I don't have to turn off debug mode--while I'm developing--and have better control over what I strip out of the console window.

In the example above, I chose to strip out blank lines (grep -e "^$" -v) and the annoying "Served asset /views.js - 304 Not Modified (0ms)" lines (grep -v "304 Not Modified").

Note that I added the --line-buffered argument to the first grep command to allow all tail output to immediately flow through the pipeline.