URL
Click on the red underlined text to get to the source
... client request must be directed. These hints may come from the URL
of the content or other parts of the MIME request header ...
... HTTP and RTSP describe the
requested content by its URL [6]. In many cases, this information
is sufficient to disambiguate the content and suitably direct the
...
... method is the performance
implications of URL-parsing in the path of the network traffic.
However, it is generally the case that the return traffic ...
... among a set of delivery nodes by content objects identified by URLs.
This allows object-specific control of server loading. For example,
requests for non-cacheable object types may be directed away from a
...
... content provider can now modify references to
embedded objects such that they could be fetched from the best
surrogate. This technique is also known as URL rewriting.
Content modification techniques must not violate the architectural
...
... operations or modifications on content.
The basic types of URL rewriting are discussed in the following
subsections.
...
... A-priori URL Rewriting ...
...
In this scheme, a content provider rewrites the embedded URLs before
the content is positioned on the origin server. In this case, URL
...
... content provider rewrites the embedded URLs before
the content is positioned on the origin server. In this case, URL
rewriting can be done either manually or by using software tools that
...
... rewriting can be done either manually or by using software tools that
parse the content and replace embedded URLs.
A-priori URL ...
... URLs.
A-priori URL rewriting alone does not allow consideration of client
specifics for Request-Routing ...
... On-Demand URL Rewriting ...
...
On-Demand or dynamic URL rewriting, modifies the content when the
client request reaches the origin server. At this time, the identity ...
... of the client is known and can be considered when rewriting the
embedded URLs. In particular, an automated process can determine,
on-demand, which surrogate would serve the requesting client best.
...
... on-demand, which surrogate would serve the requesting client best.
The embedded URLs can then be rewritten to direct the client to
retrieve the objects from the best surrogate rather than from the
...
... non-cacheable. Alternatively, such pages can be marked to be
cacheable only for a relatively short period of time. Rewritten
URLs on cached pages can cause problems, because they can get
outdated and point to surrogates that are no longer available or
no longer good choices.
...
... routing in
CNs. Specifically, when TLS is used the full URL is not visible to
the content network unless it terminates the TLS session ...
... Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738(-> 4266prop | 4248prop), December 1994. ...