Fix #2516 - Fix format detection when content-type contains charset

Even though Puppet never transmist a charset information in its
response/request content-type, some proxy (especially Apache with the
infamous AddDefaultCharset configuration) may add this "incorrect"
information.

This patch makes sure that only the mime-type is used when looking
for the format associated with a response or a request.

The patch also provides a better error message when the client or server
code is fed with a request whose mime-type can not be mapped to a known
format.

It also fixes a typo noticed by the original reporter.

Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/lib/puppet/indirector/rest.rb b/lib/puppet/indirector/rest.rb
index 4d818c986..35847de88 100644
--- a/lib/puppet/indirector/rest.rb
+++ b/lib/puppet/indirector/rest.rb
@@ -41,11 +41,13 @@ class Puppet::Indirector::REST < Puppet::Indirector::Terminus
                 raise "No content type in http response; cannot parse"
             end
 
+            content_type = response['content-type'].gsub(/\s*;.*$/,'') # strip any appended charset
+
             # Convert the response to a deserialized object.
             if multiple
-                model.convert_from_multiple(response['content-type'], response.body)
+                model.convert_from_multiple(content_type, response.body)
             else
-                model.convert_from(response['content-type'], response.body)
+                model.convert_from(content_type, response.body)
             end
         else
             # Raise the http error if we didn't get a 'success' of some kind.