What does "rewritten URL" mean in a policy trace?

book

Article ID: 167197

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

 You might see something like this in a policy trace:


 GET http://stats.rightnow.com/b/ss/rightnowglobal/1/H.20.3/s44520208596179?AQB=1&ndh=1&t=22/0/2010+13:25:18+5+300&vmt=484336AF&ce=UTF-8&ns=rightnowtechnologies&pageName=US:Home+Page:Home&g=http://www.rightnow.com/&ch=Home+Page&server=US&c1=Home+Page&h1=U
    DNS lookup was unrestricted
  rewritten URL(s):
    cache_url=http://stats.rightnow.com/b/ss/rightnowglobal/1/H.20.3/s44520208596179?AQB=1&ndh=1&t=22/0/2010%2013%3A25%3A18%205%20300&vmt=484336AF&ce=UTF-8&ns=rightnowtechnologies&pageName=US%3AHome%20Page%3AHome&g=http%3A//www.rightnow.com/&ch=Home%20Page&s

Resolution

The URL was rewritten to be normalized so there are not multiple cache objects for the same URL.  Essentially, the original URL has special characters like "+" and ":". The ProxySG normalizes the URL by using the hex escape for the characters "%20" and "%3A" respectively, thus ensuring different forms of the URL access the same cached object entry.

This is perfectly valid according to the HTTP 1.1 RFC2616 (https://tools.ietf.org/html/rfc2616#section-3.2.3)  and according to RFC 2396 (https://tools.ietf.org/html/rfc2396) on Uniform Resource Identifiers syntax.