- 19 5月, 2014 1 次提交
-
-
由 Jarmo Isotalo 提交于
As Rack has some non backwards compatible changes added required modifications to keep behaviour in rails close to same as before. Also modified generators to include rack/rack for not yet released version of rack
-
- 15 4月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
When requesting a controller with the following code with a unknown format: def my_action respond_to do |format| format.json { head :ok } format.any { render text: 'Default response' } end end we should render the default response instead of raising ActionController::UnknownFormat Fixes #14462 Conflicts: actionpack/CHANGELOG.md actionpack/test/controller/mime/respond_with_test.rb Conflicts: actionpack/CHANGELOG.md
-
- 14 2月, 2014 1 次提交
-
-
由 Łukasz Strzałkowski 提交于
-
- 13 2月, 2014 1 次提交
-
-
由 Lukasz Strzalkowski 提交于
Allow setting `request.variant` as an array - an order in which they will be rendered. For example: request.variant = [:tablet, :phone] respond_to do |format| format.html.none format.html.phone # this gets rendered end
-
- 24 12月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
TLDR: always return an object that responds to the query methods from request.format, and do not touch Mime::Type[] lookup to avoid bugs. --- Long version: The initial issue was about being able to do checks like request.format.html? for request with an unknown format, where request.format would be nil. This is where the issue came from at first in #7837 and #8085 (merged in cba05887), but the implementation went down the path of adding this to the mime type lookup logic. This unfortunately introduced subtle bugs, for instance in the merged commit a test related to send_file had to be changed to accomodate the introduction of the NullType. Later another bug was found in #13064, related to the content-type being shown as #<Mime::NullType:...> for templates with localized extensions but no format included. This one was fixed in #13133, merged in 43962d6e. Besides that, custom handlers were not receiving the proper template formats anymore when passing through the rendering process, because of the NullType addition. That was found while migrating an application from 3.2 to 4.0 that uses the Markerb gem (a custom handler that generates both text and html emails from a markdown template). --- This changes the implementation moving away from returning this null object from the mime lookup, and still fixes the initial issue where request.format.zomg? would raise an exception for unknown formats due to request.format being nil.
-
- 04 12月, 2013 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
Avoid one-liner conditionals when they are too big. Avoid concatenating strings to build error messages. Improve messages a bit.
-
由 Łukasz Strzałkowski 提交于
By default, variants in the templates will be picked up if a variant is set and there's a match. The format will be: app/views/projects/show.html.erb app/views/projects/show.html+tablet.erb app/views/projects/show.html+phone.erb If request.variant = :tablet is set, we'll automatically be rendering the html+tablet template. In the controller, we can also tailer to the variants with this syntax: class ProjectsController < ActionController::Base def show respond_to do |format| format.html do |html| @stars = @project.stars html.tablet { @notifications = @project.notifications } html.phone { @chat_heads = @project.chat_heads } end format.js format.atom end end end The variant itself is nil by default, but can be set in before filters, like so: class ApplicationController < ActionController::Base before_action do if request.user_agent =~ /iPad/ request.variant = :tablet end end end This is modeled loosely on custom mime types, but it's specifically not intended to be used together. If you're going to make a custom mime type, you don't need a variant. Variants are for variations on a single mime types.
-
- 04 3月, 2013 1 次提交
-
-
由 maximerety 提交于
Fix ActionDispatch::Request#formats on xhr requests when HTTP_ACCEPT header is empty string. About issue #7774, same fix as in commit bebb02fd but for xhr requests.
-
- 17 1月, 2013 1 次提交
-
-
由 Konstantin Papkovskiy 提交于
-
- 08 12月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 15 8月, 2012 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 24 5月, 2012 1 次提交
-
- 20 5月, 2012 1 次提交
-
-
由 Henrik Hodne 提交于
For future reference, this is the regex I used: ^\s*#\s*\n(?!\s*#). Replace with the first match, and voilà! Note that the regex matches a little bit too much, so you probably want to `git add -i .` and go through every single diff to check if it actually should be changed.
-
- 23 4月, 2012 1 次提交
-
-
由 Bogdan Gusiev 提交于
-
- 20 7月, 2011 1 次提交
-
-
由 ogeidix 提交于
An xhr request must have an "Accept" or "Content-type" header in order to be considered a request with valid_accept_header.
-
- 03 5月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 23 11月, 2010 3 次提交
-
-
由 Neeraj Singh 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
leading */* and comma Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
has ....,*/* . It is possible to a device to send request such that */* appear at the beginning of the "Accept" header. This patch ensures that "Accept" header is ignored for such cases too. Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 21 11月, 2010 2 次提交
-
-
由 Neeraj Singh 提交于
-
由 Neeraj Singh 提交于
-
- 28 8月, 2010 1 次提交
-
-
由 Joost Baaij 提交于
-
- 02 4月, 2010 1 次提交
-
-
由 Paul Sadauskas 提交于
Slightly less annoying check for acceptable mime_types. This allows Accept: application/json, application/jsonp (and the like), but still blacklists browsers. Essentially, we use normal content negotiation unless you include */* in your list, in which case we assume you're a browser and send HTML [#3541 state:resolved]
-
- 29 3月, 2010 1 次提交
-
-
由 wycats 提交于
it to return a String. Split the Rails API so that Request#content_type returns a String, and Request#content_mime_type returns a Mime::Type object.
-
- 10 3月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 16 1月, 2010 1 次提交
-
-
由 José Valim 提交于
-