# Re: Unexpected behavior with respond\_to

**URL:** <https://www.ruby-forum.com/t/re-unexpected-behavior-with-respond-to/194792>\
**Category:** Rails\
**Created:** [September 10, 2010, 7:21pm UTC](https://www.ruby-forum.com/t/re-unexpected-behavior-with-respond-to/194792 "2010-09-10T19:21:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik\_Hetzner](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/4491bb/32.png) [@Erik\_Hetzner](https://www.ruby-forum.com/u/Erik_Hetzner)\
**Post date:** [September 10, 2010, 7:21pm UTC](https://www.ruby-forum.com/t/re-unexpected-behavior-with-respond-to/194792/1 "2010-09-10T19:21:45Z")

</div>

At Mon, 6 Sep 2010 04:05:17 +0300,  
Svilen Vassilev wrote:

> Really stuck on this issue. In 2.3.8 the code worked perfectly fine.  
> Hi Svilen,

FYI:

[https://rails.lighthouseapp.com/projects/8994/tickets/5277-rails-300rc-responds-strangely-to-empty-accept-header](https://rails.lighthouseapp.com/projects/8994/tickets/5277-rails-300rc-responds-strangely-to-empty-accept-header)  
[https://rails.lighthouseapp.com/projects/8994/tickets/5278-order-of-an-accept-header-should-not-matter-to-respond\_to-rails-300rc](https://rails.lighthouseapp.com/projects/8994/tickets/5278-order-of-an-accept-header-should-not-matter-to-respond_to-rails-300rc)

I believe that rails is doing the wrong thing here, but I do not have  
time to supply a patch.

best, Erik Hetzner