<?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 Re: URL inspection on non-web browsing applications in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/url-inspection-on-non-web-browsing-applications/m-p/46558#M34225</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While URL filtering does apply to applications that are not "web-browsing", the underlying protocol must be HTTP. URL filtering only applies to traffic which has an HTTP request and response. If you had a policy that was scanning all trust-to-untrust traffic regardless of application, you could look at your URL filtering logs to see the applications present. You will see things like facebook-base, flash, youtube-base, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Greg &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2013 20:26:36 GMT</pubDate>
    <dc:creator>gwesson</dc:creator>
    <dc:date>2013-01-30T20:26:36Z</dc:date>
    <item>
      <title>URL inspection on non-web browsing applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-inspection-on-non-web-browsing-applications/m-p/46557#M34224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One of my customers asked me a question about URL inspection on non-web browsing applications. The question was, if he has a Security Policy that allows multiple applications (web and non-web) and he also has a URL Profile attached to that policy, will the firewall inspection all traffic that is allowed through that policy even though some of it is non-web traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 19:46:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-inspection-on-non-web-browsing-applications/m-p/46557#M34224</guid>
      <dc:creator>jwolach</dc:creator>
      <dc:date>2013-01-30T19:46:46Z</dc:date>
    </item>
    <item>
      <title>Re: URL inspection on non-web browsing applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-inspection-on-non-web-browsing-applications/m-p/46558#M34225</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While URL filtering does apply to applications that are not "web-browsing", the underlying protocol must be HTTP. URL filtering only applies to traffic which has an HTTP request and response. If you had a policy that was scanning all trust-to-untrust traffic regardless of application, you could look at your URL filtering logs to see the applications present. You will see things like facebook-base, flash, youtube-base, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Greg &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 20:26:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-inspection-on-non-web-browsing-applications/m-p/46558#M34225</guid>
      <dc:creator>gwesson</dc:creator>
      <dc:date>2013-01-30T20:26:36Z</dc:date>
    </item>
  </channel>
</rss>

