(no title)
markcampbell | 11 years ago
The cookie being set is unsigned according to the documentation[0] on rails, so a user could modify it and send it back to get a different cached response. Say that they saw that the user level was being set in there (like in the blog post) and they change the value to the 'staff' value to get the staff cached response. Probably not a good idea!
With that said, I don't think that this technique is adequate right now when you have user access level concerns and you're relying on that piece of unsigned information to not be tampered with.
[0] http://api.rubyonrails.org/classes/ActionDispatch/Cookies.ht...
No comments yet.