Ticket #337 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

Allow charset parameter for JSON and XML request content-types

Reported by: klazu..@gmail.com Assigned to:
Priority: major Milestone: The Future
Component: Merb Keywords: request json xml content-type charset
Cc:

Description

This defect is just like the defect outlined in Ticket #225. The problem is that when a client sends an HTTP request with Content-Type set to something like "text/xml; charset=utf-8", Merb::Request will try to do a string comparison against "text/xml" (without the charset part) and fail. The patch is nearly identical to the patch provided in Ticket #225.

Note that this patch just ignores the charset that the client provides. I don't know enough about character encoding issues or Merb to know how the framework should handle this.

Attachments

allow_charset_for_json_and_xml_requests.patch (2.9 kB) - added by klazu..@gmail.com on 11/30/07 11:28:29.

Change History

11/30/07 11:28:29 changed by klazu..@gmail.com

  • attachment allow_charset_for_json_and_xml_requests.patch added.

11/30/07 13:57:54 changed by e.@brainspl.at

  • status changed from new to closed.
  • resolution set to fixed.

(In [1057]) allow charset in the content type for json and xml requests. closes #337 , thanks klazu..@gmail.com