<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CWE-436 on ZAP</title>
    <link>/alerttags/cwe-436/</link>
    <description>Recent content in CWE-436 on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/alerttags/cwe-436/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Charset Mismatch</title>
      <link>/docs/alerts/90011-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90011-4/</guid>
      <description>&lt;p&gt;This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there&amp;rsquo;s a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content&amp;rsquo;s correct character set.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Charset Mismatch (Header Versus Meta Charset)</title>
      <link>/docs/alerts/90011-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90011-2/</guid>
      <description>&lt;p&gt;This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there&amp;rsquo;s a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content&amp;rsquo;s correct character set.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Charset Mismatch (Header Versus Meta Content-Type Charset)</title>
      <link>/docs/alerts/90011-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90011-1/</guid>
      <description>&lt;p&gt;This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there&amp;rsquo;s a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content&amp;rsquo;s correct character set.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Charset Mismatch (Meta Charset Versus Meta Content-Type Charset)</title>
      <link>/docs/alerts/90011-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90011-3/</guid>
      <description>&lt;p&gt;This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there&amp;rsquo;s a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content&amp;rsquo;s correct character set.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
