|
The Prefetch feature reduces the time required to download
and display web pages. The Prefetch client mechanism intercepts browser connections destined to ports 80 and 8080, and attempts to match them with connections already in the process of delivering content from the remote PacketShaper. The Prefetch server mechanism operates on the PacketShaper closest to the web server; it inspects all content returning from connections to ports 80 and 8080, tries to find and prefetch any embedded objects that the browser will probably request, and will immediately start pushing that content back towards the browser-side PacketShaper.
The Prefetch client and server can be enabled/disabled independently. For prefetching to work, Prefetch client support must be enabled on the PacketShaper closest to the browser machines, and Prefetch server support must be enabled on the PacketShaper closest to the web server. If there are web servers on both sides of the link and you want to provide prefetching for web connections in both directions, you can enable Prefetch client and server on both PacketShapers.
Notes:
- Prefetch works on HTTP traffic running on ports 80 or 8080.
- When Prefetch is enabled, the PacketShaper and partner
must be configured with the address of at least one DNS server.
If more than one DNS server is configured, the Prefetch logic will
spread its requests equally among them. To configure DNS servers,
see Reconfigure
Basic Settings.
- Client Prefetch forces FastStart be enabled. If FastStart isn't already enabled when you turn on client Prefetch, FastStart will automatically be set to on and the following message will alert you to this situation: "Enabling client prefetch has also enabled FastStart."
|