| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Rails 5.0 default server puma web server. following commit - https://github.com/rails/rails/commit/ae48ea69
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
Still more to do. Please assist!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`redirect_to :back` is a somewhat common pattern in Rails apps, but it
is not completely safe. There are a number of circumstances where HTTP
referrer information is not available on the request. This happens often
with bot traffic and occasionally to user traffic depending on browser
security settings.
When there is no referrer available on the request, `redirect_to :back`
will raise `ActionController::RedirectBackError`, usually resulting in
an application error.
`redirect_back` takes a required `fallback_location` keyword argument
that specifies the redirect when the referrer information is not
available. This prevents 500 errors caused by
`ActionController::RedirectBackError`.
|
|
|
|
|
|
| |
AbstractRequest has been deprecated, updating to refer to ActionDispatch::Request instead.
[ci skip]
|
| |
|
|
|
|
| |
action_controller_overview file Rails' -> Rails" [ci skip]
|
| |
|
|
|
|
| |
Followup to #20637.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|\
| |
| | |
Action Controller guide edits for grammar and clarity
|
| | |
|
| | |
|
|/
|
|
| |
- Changed `IN` to `ON` in all note sentences in guides.
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
References #18148.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This pattern is too problematic and introduces a lot of edge cases:
* On 4.2, the issue https://github.com/rails/rails/issues/15124 is
back again.
* needs to define each action for each http status otherwise the
router raises ActionController::RoutingError (No route matches).
* If the router has `match "/*username",...` and some action is
missing, Rails will pick up the "match" and try to do its job.
* encourages people to copy & paste programming. Not DRY.
[ci skip]
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
yuki24/another-improvements-for-dynamic-error-pages
A warning line should look like a warning section in Guides
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| | |
Using `get` results in an unexpected error page(returning empty body) for requests of other HTTP mehtods other than GET. Use `match ..., via:
:all` so the exceptions app can be more stable.
|
|/
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
| |
ActionController::Base
Inheriting `ApplicationController` often causes an issue as it always
has before/after actions. It should encourage to use `ActionController::Base` instead.
[ci skip]
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
* Should say "sensitive" instead of "sensible"
|
| |
|
|
|
|
|
|
|
| |
References to ``AppName::Application` removed in favour of ``Rails.application``
as generated with a new rails 4.1 app.
[ci skip]
|
|
|
| |
This is in the note at the end of Section 2: Controller Naming Convention. [ci skip]
|
|
|
|
| |
Closes #14409
|
|
|
|
| |
controller guide
|
|
|
|
|
| |
* Introduces `:plain`, `:html`, `:body` render option.
* Update guide to use `render :plain` instead of `render :text`.
|
|
|
|
| |
Also added a `cookies_serializer.rb` initializer to the app template.
|
| |
|
|
|
|
|
| |
Rename allowed options to :marshal and :json, for custom serializers
only allow the use of custom classes.
|
|
|
|
|
|
|
|
|
| |
The api for filters with classes change and the guides weren't updated.
Now the class must respond for methods with the same name as the filter,
so the `before_action` calls a `before` method, and so on.
The method `#filter` has been deprecated in 4.0.0 and has been removed
in 4.1.0: #7560
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MessageEncryptor has :serializer option, where any serializer object can
be passed. This commit make it possible to set this serializer from configuration
level.
There are predefined serializers (:marshal_serializer, :json_serialzier)
and custom serializer can be passed as String, Symbol (camelized and
constantized in ActionDispatch::Session namepspace) or serializer object.
Default :json_serializer was also added to generators to provide secure
defalt.
|
|
|
|
|
|
|
|
| |
deep_munge solves CVE-2013-0155 security vulnerability, but its
behaviour is definately confuisng. This commit adds logging to deep_munge.
It logs keys for which values were set to nil.
Also mentions in guides were added.
|
| |
|
|
|
|
| |
Also make all three examples consistent.
|
| |
|
|
|
|
|
|
|
|
|
| |
[ci skip]
This is a follow up to #12609 and integrates #12158.
Thanks @aspiers.
Closes #12158.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
activesupport/lib/active_support/core_ext/hash/deep_merge.rb
activesupport/lib/active_support/core_ext/hash/keys.rb
|