Hi Hans, minor point:
+ FIXME("(%s, %s)\n", debugstr_w(s1), debugstr_w(s2));
Shouldn't that be TRACE? --Juan
On Thursday 29 January 2009 17:18:35 Juan Lang wrote:
- FIXME("(%s, %s)\n", debugstr_w(s1), debugstr_w(s2));
Shouldn't that be TRACE?
No, we should have a warning because the algorithm is unknown and the tests are not exhaustive.
-Hans
No, we should have a warning because the algorithm is unknown and the tests are not exhaustive.
Fair enough. This is an implementation of the same origin policy, yes? Wikipedia provides some interesting examples, for instance, having different port numbers in the same domain can cause a mismatch: http://en.wikipedia.org/wiki/Same_origin_policy --Juan
On Thursday 29 January 2009 17:51:26 Juan Lang wrote:
No, we should have a warning because the algorithm is unknown and the tests are not exhaustive.
Fair enough. This is an implementation of the same origin policy, yes? Wikipedia provides some interesting examples, for instance, having different port numbers in the same domain can cause a mismatch: http://en.wikipedia.org/wiki/Same_origin_policy
I think so yes, although this function seems to be more narrow in scope; it's not about full URLs but rather about domains, ie. the parts of a URL that a cookie is associated with.
-Hans
-
Hans Leidekker -
Juan Lang