<?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 PIX 6.1.1 websense long-url bug workaround in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-6-1-1-websense-long-url-bug-workaround/m-p/21807#M679553</link>
    <description>&lt;P&gt;I have a PIX 515 running OS 6.1.1.  It is setup to use a websense server on the internal lan for URL filtering.  Whenever a user attempts to access a very long URL such as those created by mapquest and travelocity (and many other site) the site times out.  When the user clicks refresh the site immediately comes up properly.  This happens for every long URL of around 1500 characters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to BUG CSCdt17577 &amp;amp; CSCdu39312 this is a known issue.  The bug report says that it is first fixed in 6.1.1 which is what I am running.  It says that there is a workaround to "Introduce the new keyword "long-url" which let bypass the&lt;/P&gt;&lt;P&gt;url filtering if the URL is too long."  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't find any information about how to use this "long-url" feature to rid myself of this problem.  Does anyone else use websense and have this problem?  Does anyone know how to use this "long-url" keyword? I put in several exception lines as they suggested, but users seem to come up with new sites every day so I would like to have a more general solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:jkrueger@bcsc.com" target="_blank"&gt;jkrueger@bcsc.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;CCNP&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:56:31 GMT</pubDate>
    <dc:creator>jjkruege</dc:creator>
    <dc:date>2020-02-21T05:56:31Z</dc:date>
    <item>
      <title>PIX 6.1.1 websense long-url bug workaround</title>
      <link>https://community.cisco.com/t5/network-security/pix-6-1-1-websense-long-url-bug-workaround/m-p/21807#M679553</link>
      <description>&lt;P&gt;I have a PIX 515 running OS 6.1.1.  It is setup to use a websense server on the internal lan for URL filtering.  Whenever a user attempts to access a very long URL such as those created by mapquest and travelocity (and many other site) the site times out.  When the user clicks refresh the site immediately comes up properly.  This happens for every long URL of around 1500 characters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to BUG CSCdt17577 &amp;amp; CSCdu39312 this is a known issue.  The bug report says that it is first fixed in 6.1.1 which is what I am running.  It says that there is a workaround to "Introduce the new keyword "long-url" which let bypass the&lt;/P&gt;&lt;P&gt;url filtering if the URL is too long."  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't find any information about how to use this "long-url" feature to rid myself of this problem.  Does anyone else use websense and have this problem?  Does anyone know how to use this "long-url" keyword? I put in several exception lines as they suggested, but users seem to come up with new sites every day so I would like to have a more general solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:jkrueger@bcsc.com" target="_blank"&gt;jkrueger@bcsc.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;CCNP&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:56:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-6-1-1-websense-long-url-bug-workaround/m-p/21807#M679553</guid>
      <dc:creator>jjkruege</dc:creator>
      <dc:date>2020-02-21T05:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 6.1.1 websense long-url bug workaround</title>
      <link>https://community.cisco.com/t5/network-security/pix-6-1-1-websense-long-url-bug-workaround/m-p/21808#M679559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you.  If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (&lt;A class="jive-link-custom" href="http://www.cisco.com/tac" target="_blank"&gt;http://www.cisco.com/tac&lt;/A&gt;) or speak with a TAC engineer.  You can open a TAC case online at &lt;A class="jive-link-custom" href="http://www.cisco.com/tac/caseopen" target="_blank"&gt;http://www.cisco.com/tac/caseopen&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone else in the forum has some advice, please reply to this thread.&lt;/P&gt;&lt;P&gt;	&lt;/P&gt;&lt;P&gt;Thank you for posting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2002 01:33:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-6-1-1-websense-long-url-bug-workaround/m-p/21808#M679559</guid>
      <dc:creator>ciscomoderator</dc:creator>
      <dc:date>2002-01-03T01:33:37Z</dc:date>
    </item>
  </channel>
</rss>

