-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/23/12 4:39 PM, Yoav Nir wrote:
This is to initiate WGLC for the X-Frame-Options draft
Lacking time for a thorough review, I'll provide only a few small
suggestions (take them or leave them as you will)...
Abstract
this standard defines =
Here is my review (with my co-chair hat off):
[RFC3986] should be a Normative reference (as it is required to
parse/generate
a valid X-Frame-Options header field).
[RFC6454] is normative, because there is a SHOULD requirement to use it.
In Section 2.1:
The ALLOW-FROM URI MUST be valid.
I
On 2012-11-06 00:19, Alexey Melnikov wrote:
Here is my review (with my co-chair hat off):
[RFC3986] should be a Normative reference (as it is required to
parse/generate
a valid X-Frame-Options header field).
[RFC6454] is normative, because there is a SHOULD requirement to use it.
In Section
Hi all
This is to initiate WGLC for the X-Frame-Options draft (not to be confused with
the Frame-Options draft).
Please go to http://tools.ietf.org/html/draft-ietf-websec-x-frame-options-01,
read the draft and send comments.
As usual, we would very much like to hear comments about clarity,
