<?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: blogspot.com application in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/blogspot-com-application/m-p/48651#M35830</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Should be possible if you send in this as a request to the appid-team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise I think you can do this yourself with a custom url-category.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My opinion regarding pr0nsites and blocking is that this is the bad method to handle the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inform and educate the users what you as an organisation except from them (like that the rest of the world will see that someone from your place is browsing these sites, at least the siteowners) - for example through policies. And then use continue page (and inform on that page the current policy or such) instead of blockpage so if the urlcategory brings you a false positive the client can still bypass the "block".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way you will also avoid the trashtalk regarding "censorship" (since the continuepage informs the client that this is a page which is violating current policy etc so its not censorship but rather help the client to make a good decision (there can be reasons for why someone visits a specific site)).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also whats placed in the category "adult-and-pornography" is up to the one who maintains the urlcategory database (currently brightcloud) which means that stuff like the frontpage of www.playboy.com belongs to this category. However you will see more nudity at www.youtube.com than what playboy shows on their frontpage (I guess you get the nuditypart once you login).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: &lt;A href="http://www.paloaltonetworks.com/researchcenter/tools/"&gt;http://www.paloaltonetworks.com/researchcenter/tools/&lt;/A&gt; and click on "Submit an App" so get in contact with the appid-team.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Feb 2012 07:51:38 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2012-02-09T07:51:38Z</dc:date>
    <item>
      <title>blogspot.com application</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blogspot-com-application/m-p/48650#M35829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'd like to differenciate blogspot.com websites that contain adult content from others blogspot.com sites.&lt;/P&gt;&lt;P&gt;I noticed&amp;nbsp; that blogspot.com adult content sites redirect the requested url to a page for content acceptance.&lt;/P&gt;&lt;P&gt;Is possible to block this behavior with a custom application ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Feb 2012 07:58:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blogspot-com-application/m-p/48650#M35829</guid>
      <dc:creator>helenio.sartori</dc:creator>
      <dc:date>2012-02-08T07:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: blogspot.com application</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blogspot-com-application/m-p/48651#M35830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Should be possible if you send in this as a request to the appid-team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise I think you can do this yourself with a custom url-category.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My opinion regarding pr0nsites and blocking is that this is the bad method to handle the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inform and educate the users what you as an organisation except from them (like that the rest of the world will see that someone from your place is browsing these sites, at least the siteowners) - for example through policies. And then use continue page (and inform on that page the current policy or such) instead of blockpage so if the urlcategory brings you a false positive the client can still bypass the "block".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way you will also avoid the trashtalk regarding "censorship" (since the continuepage informs the client that this is a page which is violating current policy etc so its not censorship but rather help the client to make a good decision (there can be reasons for why someone visits a specific site)).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also whats placed in the category "adult-and-pornography" is up to the one who maintains the urlcategory database (currently brightcloud) which means that stuff like the frontpage of www.playboy.com belongs to this category. However you will see more nudity at www.youtube.com than what playboy shows on their frontpage (I guess you get the nuditypart once you login).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: &lt;A href="http://www.paloaltonetworks.com/researchcenter/tools/"&gt;http://www.paloaltonetworks.com/researchcenter/tools/&lt;/A&gt; and click on "Submit an App" so get in contact with the appid-team.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2012 07:51:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blogspot-com-application/m-p/48651#M35830</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-02-09T07:51:38Z</dc:date>
    </item>
  </channel>
</rss>

