rails-prg 0.1.0
Secure applications must not use browser history or cache, this can cause problems with some browsers when following standard Rails pattern for POST -> Error -> Render -> Success -> Redirect. For full protection from ERR_CACHE_MISS (in Chrome with no-cache, no-store), Rails should redirect on errors as well as on success, always following full POST-REDIRECT-GET pattern. This way the browser will always have a consistent back-button history to traverse without triggering browser errors unable to display form submission pages.
Gemfile:
=
Copier
Copié!
installation:
=
Dépendances de Runtime (2):
actionpack
>= 0
railties
>= 0
Dépendances de Development (11):
activerecord
>= 0
bundler
~> 1.5
cane
>= 0
capybara
>= 0
database_cleaner
>= 0
rake
>= 0
rspec-rails
>= 0
selenium-webdriver
>= 0
simplecov
>= 0
sprockets-rails
>= 0
sqlite3
>= 0
Propriétaires:
Auteurs:
-
Tom Meier
Total de contrôle SHA 256:
52d81df81b3ba7ae37b83546543aa0894739a44e2a9eced57353d1b409e1ede2