RE: ACTION-902 (Reprise) Summarise and prepare proposed resolutions on HTTPS link rewriting. from Robert Finean on 2009-03-19 (public-bpwg@w3.org from March 2009)

From: Robert Finean <Rob.Finean@openwave.com>
Date: Thu, 19 Mar 2009 14:25:46 -0000
To: "Sullivan, Bryan" <BS3131@att.com>
Cc: "Public MWBP" <public-bpwg@w3.org>
Message-ID: <7F652B9B6A93184AB38BBCF677E7287A059E2BC4@bfs-exch-prd1.myopwv.com>

Hi Bryan,

I don't understand this rationale:

<<
2) PROPOSED RESOLUTION: Proxies MAY rewrite links, where content
transformation is permitted, providing that content domain origin
distinctions are preserved by the proxy.
-1 : Rationale is that scalability and basic ability to dynamically
extend the link rewriting support to new sites will prevent a subdomain
approach from being feasible. Link rewriters that I have worked with use
URL path tokens associated with the original URI, which is scalable
since there is no dependency upon DNS.
>>

Can you explain please (maybe an example)?

thanks,

ROb

Received on Thursday, 19 March 2009 14:26:34 UTC