<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Change to HTTP decoder in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/change-to-http-decoder/m-p/133244#M47187</link>
    <description>&lt;P&gt;Did I miss a notice that the http decoder was being changed so that most of my rules based on the web-browsing app would break?&amp;nbsp; Nearly all of my web-browsing traffic is suddenly being identified as unknown-tcp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I notice in the release notes for 646 app update that the http decoder was modified.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Dec 2016 13:45:50 GMT</pubDate>
    <dc:creator>epeeler</dc:creator>
    <dc:date>2016-12-16T13:45:50Z</dc:date>
    <item>
      <title>Change to HTTP decoder</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/change-to-http-decoder/m-p/133244#M47187</link>
      <description>&lt;P&gt;Did I miss a notice that the http decoder was being changed so that most of my rules based on the web-browsing app would break?&amp;nbsp; Nearly all of my web-browsing traffic is suddenly being identified as unknown-tcp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I notice in the release notes for 646 app update that the http decoder was modified.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2016 13:45:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/change-to-http-decoder/m-p/133244#M47187</guid>
      <dc:creator>epeeler</dc:creator>
      <dc:date>2016-12-16T13:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Change to HTTP decoder</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/change-to-http-decoder/m-p/133409#M47215</link>
      <description>With every content update a release note email is sent out if you opted in from your support account&lt;BR /&gt;&lt;BR /&gt;But the behavior you describe does not sound "as expected" so something possibly went wrong, maybe the content package installation failed in the backend &lt;BR /&gt;Have you tried rolling back, redownloading and reinstalling?</description>
      <pubDate>Sun, 18 Dec 2016 21:35:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/change-to-http-decoder/m-p/133409#M47215</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-12-18T21:35:23Z</dc:date>
    </item>
  </channel>
</rss>

