Internet Explorer Accept header

There is nothing in Rails 3 addressing this issue as far as I can see. I don't think this belongs in Rack, it's coupled with the way Rails does content negotiation.

The fix in 3.0 is to reject Accept header usage if more than one MIME is specified.

This means that:

Accept: text/html

will work, but:

Accept: rather/retarded, ie/header

will fall back to text/html.

fwiw, this is why I added use_accept_header = false. It's a nice science experiment, but the header's basically junk in the wild.

I tested applying this patch to rails 2.3.5 and this causes Internet Explorer to fail to respond to certain requests, for example:

def update_chat
@shouts = Shout.recent

respond_to do |format|

format.js

end end

This method, which only responds to javascript, fails with Internet Explorer once this patch is applied, as Internet Explorer responds to the first mime type, which is text/html with this patch, which does not exist in this method..

Could this be improved by adopting some kind of qs (quality of source) parameter to the format.* call, in the same way as Apache's content negotiation works?

repond_to do |format|
  format.html
  format.jpg :qs => 0.8 do
    send_file @photo.public_path, :type => 'image/jpeg'
  end
end

You would have to ensure that
- A MIME type match by extension would automatically match its exact format block - A request without an extension would be matched by a q/qs algorithm like that in Apache's content negotiation - Suitable default qs values were set for different MIME types to reflect that a) Rails prefers serving HTML documents b) Some browsers aren't very good at specifying their Accept header

By this logic, a UA wanting to get a non-HTML response to an extensionless URI would have to either
- Supply a q

For example, Firefox supplies a different Accepts header for resources loaded through an tag

Is this heading in the wrong direction? It seems to me that the Accept header is at most a guideline, so there shouldn't be any problem with using our own values to fudge the browser's requested quality values. The only problem would be doing the maths to work out the best possible 'fudge' values

Any updates to this ticket? Is somebody working on a new patch?

I have the same issue, but "IE Accept header related bugs" been fixed be remove this chunk of js code:
$("form").submit(function(){

$('input[type=submit]').attr('disabled', 'disabled');
return true;

});

It's weird for me, because I was looking for an issue in server-side code.
please be ensure that all is ok with your client-side scripts.

Same problem in rails 3 with IE if having an action that can return the data in .xls format.

This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.