ACTION-781: Enact changes sugegsted by the previous 4 resolutions
Enact changes sugegsted by the previous 4 resolutions
- State:
- closed
- Person:
- Jo Rabin
- Due on:
- June 23, 2008
- Created on:
- June 16, 2008
- Associated Product:
- Guidelines for Web Content Transformation Proxies
- Related emails:
- Content Transformation Guidelines 1m (Rev 13) nearly now all 'ship shape and Bristol fashion' (from jrabin@mtld.mobi on 2008-07-22)
- Content Transformation Guidelines 1m (Rev 13) [was Re: Content Transformation Guidelines 1l (Rev 12) and Change List] (from jrabin@mtld.mobi on 2008-07-22)
- RE: Content Transformation Guidelines 1l (Rev 12) and Change List (from SPatterson@Novarra.com on 2008-07-18)
- [minutes] CT Call Tuesday 15 July 2008 (from fd@w3.org on 2008-07-15)
- RE: [agenda] CT Call Tuesday 15 July 2008 (from Rob.Finean@openwave.com on 2008-07-15)
- [agenda] CT Call Tuesday 15 July 2008 (from fd@w3.org on 2008-07-15)
- Content Transformation Guidelines 1l (Rev 12) and Change List (from jrabin@mtld.mobi on 2008-07-11)
- [minutes] BPWG F2F in Sophia, day 1 (from fd@w3.org on 2008-06-17)
Related notes:
Namely:
RESOLUTION: Regarding ISSUE-241, in the CT guidelines we should state that when the proxy makes a request for a linked resource to a new "web site", then what's in section 4.1.2 should happen (allowing for different heuristics for determining whether request is to a different or the same "web site" but giving "hitting a new domain name" as a good example. And remove the word "session" from the previous resolution on 4.1.2.
RESOLUTION: Regarding ISSUE-241, in the CT guidelines we agree that the proxy does not have to taste every linked resource (for the sake of clarity).
RESOLUTION: For CT guidelines, except in the case of https, the content transformation guidelines document does not differentiate between URI rewriting and so-called "transparent" proxy operation.
RESOLUTION: re. ISSUE-255, drop mention of examination of URI from 4.1.2 as it's a heuristic to scope rejected 200 responses, detailed in 4.4, and 4.1.2 already precises to examine the response (with a link to 4.4)
Display change log.