mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
No use case handy for justifying fresh? any more
This commit is contained in:
parent
d85a7aecbb
commit
6fae0a0ec0
2 changed files with 1 additions and 6 deletions
|
@ -1,6 +1,6 @@
|
|||
*Edge*
|
||||
|
||||
* Added stale?/fresh? and fresh_when methods to provide a layer of abstraction above request.fresh? and friends [DHH]. Example:
|
||||
* Added stale? and fresh_when methods to provide a layer of abstraction above request.fresh? and friends [DHH]. Example:
|
||||
|
||||
class ArticlesController < ApplicationController
|
||||
def show_with_respond_to_block
|
||||
|
|
|
@ -1096,11 +1096,6 @@ module ActionController #:nodoc:
|
|||
!request.fresh?(response)
|
||||
end
|
||||
|
||||
# The opposite of stale? provided for parity when that feels more natural.
|
||||
def fresh?(options)
|
||||
!stale?(options)
|
||||
end
|
||||
|
||||
# Sets the etag, last_modified, or both on the response and renders a
|
||||
# "304 Not Modified" response if the request is already fresh.
|
||||
#
|
||||
|
|
Loading…
Reference in a new issue