i cannot really upgrade. I would love too, but i have a bazillion lines
of
code for this version running.
you were right. terminology was wrong expire_after not expires…
At the VERY least, you should upgrade to Rails 2.3.18 as there were
security fixes in every one of those 9 updates (some of them quite
serious!).
Speaking as someone who also has a client with many lines of code
running in a Rails 2.3.18 framework-based application, you can really
upgrade (a little bit).
i cannot really upgrade. I would love too, but i have a bazillion lines of
code for this version running.
At the very least consider upgrading to 2.3.18 (last in the line) for
the security fixes. You’ll see deprecation warnings but your code
should work as is.
Also, assuming you’re on Ruby 1.8.7, consider moving to the 1.4.x
branch of Rubinius, which is 1.8.7 compatible and still maintained.
you were right. terminology was wrong expire_after not expires…
tested and working now, thanks very much !
i cannot really upgrade. I would love too, but i have a bazillion lines of
code for this version running.
you were right. terminology was wrong expire_after not expires…
So expires_after worked correctly in webrick. Very strange.
Colin
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.