title: Overriding Meta Character Encoding Declarations
body: <p>I know that declaring the charset of a page using the older style, like so:</p>
  
  <pre><code>&lt;meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /&gt;
  </code></pre>
  
  <p>will override any declarations of the charset of a page using the newer style, like so:</p>
  
  <pre><code>&lt;meta charset="utf-8" /&gt;
  </code></pre>
  
  <p>but I am wondering what will two of the older-style declarations do? Is the first one taken over the second? Is the second taken over the first? Or are they both omitted and simply excluded from the remainder of the algorithm that determines the actual encoding of the page.</p>
  
  <p><br>
  <strong>Example</strong></p>
  
  <p>As an example, I am wondering which character encoding declaration in the below snippet will be accepted and factored into the algorithm that determines the page's character encoding:</p>
  
  <pre><code>&lt;head&gt;
      &lt;meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /&gt;
      &lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
      ...
  &lt;/head&gt;
  </code></pre>
  
  <p><br/></p>
  
  <p>I was unable to find the answer to this in the specs or any other reputable source of documentation (though I could have missed it). </p>
  
  <p><br/></p>
  
  <p><strong>Side-Note</strong></p>
  
  <p>I am not asking this question because of a difficulty with properly setting a page's character encoding, but rather because I am curious about the answer and whether or not browsers prefer the first or second declaration. As such, alternative solutions/workarounds will not be viable answers for this question. </p>
  
  <p>Thanks for your help! Happy coding! :)</p>