{"push_id":1078615616,"size":1,"distinct_size":1,"ref":"refs/heads/ticket/master/PUP-3941-exclude-yaml-from-accept-header","head":"b7c72a7f00dffb2c914ff81f5f32183a3cad6562","before":"78dfd879ccd08e25829339471e40719634970121","commits":[{"sha":"b7c72a7f00dffb2c914ff81f5f32183a3cad6562","author":{"email":"c028c213ed5efcf30c3f4fc7361dbde0c893c5b7@puppetlabs.com","name":"Josh Cooper"},"message":"(PUP-3941) Exclude yaml from the Accept header\n\nWhen making REST requests, the agent would include `yaml` in the HTTP Accept\nheader. However we removed network support for yaml in PUP-3272. In\nparticular, the Puppet::Network::HTTP::Request#assert_supported_format\nmethod (on the server) will fail the request if it ever tries to return\nyaml. Since the server should never return it (since 4.0) and 4.0 agents\ncan't communicate with 3.x masters (due to URL prefix changes), there's no\npoint in asking for it.\n\nThis commit strips `yaml` and `b64_zlib_yaml` from the HTTP Accept header\nwhen making REST requests. It doesn't affect callers making direct\nPuppet::Network::HTTP requests, e.g. providers, report processors.","distinct":true,"url":"https://api.github.com/repos/joshcooper/puppet/commits/b7c72a7f00dffb2c914ff81f5f32183a3cad6562"}]}