Comment 3 for bug 1320276

Steve Heyman (sheyman) wrote :

Yes this one does look like the same problem that was fixed in

If there is a use case or scenario that the existing CR doesn't cover then we need to address that.

However, if it is the same case then I will suggest that is sufficient because:

1) it doesn't penalize (with additional pathlength) those who do pass in content type of application/json

2) it doesn't change the user's content type, but rather just ensure that we can read in and parse the JSON code

Ideally the fix for all of this would be for pecan (actually webob) to change their default content type from application-x-www-form-urlencoded to application/json.