ISSUE-182
We have lost the "secure page" definition
- State:
- CLOSED
- Product:
- wsc-xit
- Raised by:
- Thomas Roessler
- Opened on:
- 2008-02-05
- Description:
- While merging in the rewritten TLS-related part, we seem to have lost the secure page definition. The last version of this definition is in the published working draft here:
http://www.w3.org/TR/wsc-xit/#tlstosecurecontent
Text:
>>>
This section is normative.
If a given Web page consists of a single resource only, then all content that the user interacts with has security properties derived from the HTTP transaction used to retrieve the content.
[Definition: A Web page is called TLS-secured if the top-level resource and all other resources that can affect or control the page's content and presentation have been retrieved through strongly TLS protected HTTP transactions.]
This definition implies that inline images, stylesheets, script content, and frame content for a secure page need to be retrieved through strongly TLS protected HTTP tansactions in order for the overall page to be considered TLS-secured.
>>> - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-182: We have lost the 'secure page' definition [wsc-xit] (from tlr@w3.org on 2008-03-07)
- Re: ISSUE-182: We have lost the 'secure page' definition [wsc-xit] (from Mary_Ellen_Zurko@notesdev.ibm.com on 2008-03-07)
- Re: ISSUE-182: We have lost the 'secure page' definition [wsc-xit] (from tlr@w3.org on 2008-03-04)
- Meeting record: WSC WG face-to-face 2008-02-05 (from tlr@w3.org on 2008-02-27)
- Draft minutes: face-to-face 2008-02-05 (from tlr@w3.org on 2008-02-14)
- ISSUE-182: We have lost the 'secure page' definition [wsc-xit] (from sysbot+tracker@w3.org on 2008-02-05)
Related notes:
No additional notes.
Display change log