- From: Thomas Roessler <tlr@w3.org>
- Date: Thu, 16 Apr 2009 11:53:17 +0200
- To: WSC WG public <public-wsc-wg@w3.org>
Received on Thursday, 16 April 2009 09:53:28 UTC
Here are the situations that I think we need to exercise: 1. inline content. Page with (a) img, (b) script, (c) iframe, (d) frameset, where source URI comes from (i) different origin, (ii) same origin. 2. XHR. Page with same-origin XHR, page with foreign-origin XHR (where supported). For all these cases, we need to look at the following error conditions: - toplevel page has clean TLS, dependent resource causes TLS error. - toplevel page has TLS error, user clicks through, dependent resource causes same TLS error. - toplevel page has TLS error, user clicks through, dependent resource causes different TLS error. (These two are only usefully distinct for same-origin dependent resources.) - toplevel page has HTTP, dependent resource causes TLS error. Am I forgetting anything? -- Thomas Roessler, W3C <tlr@w3.org>
Received on Thursday, 16 April 2009 09:53:28 UTC