<?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: Ip Spoofing in Cisco Cache in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ip-spoofing-in-cisco-cache/m-p/53153#M575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This question does not specify which IP address should be spoofed.   Perhaps an explanation of WCCP and caching &lt;/P&gt;&lt;P&gt;will answer the question.&lt;/P&gt;&lt;P&gt;With WCCP enabled, the traffic passing through the 3640 router will be redirected to the CacheEngine.  The CacheEngine&lt;/P&gt;&lt;P&gt;will then check to see if it has the objects being requested.  If so it will "spoof" the web-servers address, and &lt;/P&gt;&lt;P&gt;respond to the client.  In this way the client thinks it is getting a response from the web-server.&lt;/P&gt;&lt;P&gt;If the CacheEngine does not have the object requested in its cache, then it will retrieve this content from the web-server and&lt;/P&gt;&lt;P&gt;then "spoof" the web-servers address and response to the client.  The connection from the CacheEngine to the web-server&lt;/P&gt;&lt;P&gt;will use the IP address of the CacheEngine and NOT the address of the original client making the request.  The result&lt;/P&gt;&lt;P&gt;of this is that the web-server will only see requests from one ip address for the entire organization using that CacheEngine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Feb 2002 00:21:31 GMT</pubDate>
    <dc:creator>deheron</dc:creator>
    <dc:date>2002-02-21T00:21:31Z</dc:date>
    <item>
      <title>Ip Spoofing in Cisco Cache</title>
      <link>https://community.cisco.com/t5/application-networking/ip-spoofing-in-cisco-cache/m-p/53152#M574</link>
      <description>&lt;P&gt;Is there any way to enable ip spoofing in CIsco Cache Engine.We are Using Cisco Cache Engine with 3640 router???&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2002 05:42:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ip-spoofing-in-cisco-cache/m-p/53152#M574</guid>
      <dc:creator>sunil.goel</dc:creator>
      <dc:date>2002-01-17T05:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: Ip Spoofing in Cisco Cache</title>
      <link>https://community.cisco.com/t5/application-networking/ip-spoofing-in-cisco-cache/m-p/53153#M575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This question does not specify which IP address should be spoofed.   Perhaps an explanation of WCCP and caching &lt;/P&gt;&lt;P&gt;will answer the question.&lt;/P&gt;&lt;P&gt;With WCCP enabled, the traffic passing through the 3640 router will be redirected to the CacheEngine.  The CacheEngine&lt;/P&gt;&lt;P&gt;will then check to see if it has the objects being requested.  If so it will "spoof" the web-servers address, and &lt;/P&gt;&lt;P&gt;respond to the client.  In this way the client thinks it is getting a response from the web-server.&lt;/P&gt;&lt;P&gt;If the CacheEngine does not have the object requested in its cache, then it will retrieve this content from the web-server and&lt;/P&gt;&lt;P&gt;then "spoof" the web-servers address and response to the client.  The connection from the CacheEngine to the web-server&lt;/P&gt;&lt;P&gt;will use the IP address of the CacheEngine and NOT the address of the original client making the request.  The result&lt;/P&gt;&lt;P&gt;of this is that the web-server will only see requests from one ip address for the entire organization using that CacheEngine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Feb 2002 00:21:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ip-spoofing-in-cisco-cache/m-p/53153#M575</guid>
      <dc:creator>deheron</dc:creator>
      <dc:date>2002-02-21T00:21:31Z</dc:date>
    </item>
  </channel>
</rss>

