On 07/04/09 07:36, Daniel Veditz wrote:
Maybe this does point out the need for some kind of version number in the header, so future browsers can take appropriate action when encountering an old header. For example, assuming "none" for any newly added types.
I much prefer forwardly-compatible designs to version numbers. I think the current design is forwardly-compatible, as long as we maintain a well-signposted public page listing which category all sorts of request fall into, and add new request types well before they get implemented by anyone.
For example, if a <3dvideo> tag, for which you needed red-blue glasses, made it into a draft HTML5 spec, we would decide and say loudly that this was included in "media-src" well before anyone actually implemented it.
Can you suggest a scenario in which version numbers would help? Gerv _______________________________________________ dev-security mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security
