Issue #7884 has been updated by Martin Marcher.
I think your client is doing it wrong. >From [RFC2616 14.1 Accept][1]: <blockquote> If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then the server SHOULD send a 406 (not acceptable) response. </blockquote> This is also what seems more practical to me. The abscence of an `Accept`-Header just tells me that while writing the client I didn't care what comes back, just give it to me. [1]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html ---------------------------------------- Bug #7884: Puppet should return HTTP 406 when no Accept: client request header is present https://projects.puppetlabs.com/issues/7884 Author: Jeff McCune Status: Accepted Priority: Normal Assignee: Category: Target version: Telly Affected Puppet version: Keywords: Branch: Reported from a customer. Rather than returning HTTP 400 when no Accept: header is set, Puppet should return: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Section 10.4.7 406 Not Acceptable The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
