Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Rails 3.0.0.RC responds strangely to empty Accept header

#5277

If an HTTP client fails to supply an Accept header, this should, I think, be considered equivalent to a "*/*" Accept header. From RFC 2616, section 14.1:

If no Accept header field is present, then it is assumed that the client accepts all media types.

Attached is a patch that adds a (failing) test for this behavior.

Reported by Erik Hetzner · August 2nd, 2010 @ 11:14 PM

State: open
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Ryan Bigg
    Ryan Bigg
    • State changed from new to needs-more-info
    • Importance changed from to Low

    Please confirm that this is still an issue on 3.0.

    October 11th, 2010 @ 02:09 AM

  2. Erik Hetzner
    Erik Hetzner

    My test still fails with the latest from git.

    Attaching a patch according to instructions at https://rails.lighthouseapp.com/projects/8994/sending-patches

    October 11th, 2010 @ 03:19 AM

  3. Ryan Bigg
    Ryan Bigg
    • State changed from needs-more-info to open

    Thank you, I'll mark this as open.

    October 11th, 2010 @ 03:22 AM

  4. Ryan Bigg
    Ryan Bigg

    Automatic cleanup of spam.

    October 19th, 2010 @ 08:24 AM

  5. Santiago Pastorino
    Santiago Pastorino

    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.

    February 2nd, 2011 @ 04:48 PM

  6. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:48 PM

  7. Erik Hetzner
    Erik Hetzner
    • State changed from stale to open

    Yes, my submitted test still fails with the latest 3-0-stable branch. No new information.

    [state:open]

    February 2nd, 2011 @ 08:19 PM

  8. rails
    rails

    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.

    May 3rd, 2011 @ 01:00 AM

  9. rails
    rails
    • State changed from open to stale

    May 3rd, 2011 @ 01:00 AM

  10. Erik Hetzner
    Erik Hetzner

    Still an issue. Attaching a new failing test against master.

    May 3rd, 2011 @ 05:50 PM

  11. Erik Hetzner
    Erik Hetzner
    • State changed from stale to open

    [state:open]

    May 3rd, 2011 @ 05:51 PM