title: what is the correct charset for a application/pdf content-type http response header?
body: <p>I'm looking to see whether this is correct as an HTTP response header</p>
  <pre><code>  Content-Type: application/pdf; charset=ISO-8859-1
  </code></pre>
  <p>or we should be emitting this instead</p>
  <pre><code>  Content-Type: application/pdf
  </code></pre>
  <p>I believe the latter is correct, given this:</p>
  <blockquote>
  <p>The &quot;charset&quot; parameter is used with some media types to define the
  character set (section 3.4) of the data. When no explicit charset<br />
  parameter is provided by the sender, media subtypes of the &quot;text&quot;<br />
  type are defined to have a default charset value of &quot;ISO-8859-1&quot; when
  received via HTTP. Data in character sets other than &quot;ISO-8859-1&quot; or<br />
  its subsets MUST be labeled with an appropriate charset value.<br />
  <a href="http://www.ietf.org/rfc/rfc2068.txt" rel="nofollow noreferrer">rfc2068 HTTP/1.1</a></p>
  </blockquote>
  <p>And that <a href="https://www.rfc-editor.org/rfc/rfc3778" rel="nofollow noreferrer">rfc3778  The application/pdf Media Type</a> doesn't mention charsets at all.</p>
  <p>This SO discussion is where I started, but isn't specifically about application/pdf:
  <a href="https://stackoverflow.com/questions/6913410/is-it-categorically-wrong-to-send-a-charset-parameter-with-a-content-type-header">Is it categorically wrong to send a charset parameter with a Content-Type header for non-text media types?</a></p>
  <p>Can anyone confirm or deny or point me to a better RFC?</p>