[Webkit-unassigned] [Bug 24987] Cookies set to .nhs.uk are blocked/not served

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=24987





------- Comment #4 from mrowe at apple.com  2009-04-02 12:17 PDT -------
(In reply to comment #3)
> This is where bugs like this get frustrating. I don't personally know the code
> for Safari or Webkit obviously. Having posted on Apples forums the reply I
> received was that they understand that WebKit handled the cookies, and they
> pointed to other bugs within the WebKit bug tracker to back this up.

End users aren't expected to know exactly which parts of which frameworks are
responsible for specific behaviour.  Filing a bug report against one that seems
like it may be the right place, such as WebKit, is a great way to find out
where the bug belongs.  In this case WebKit did seem like an obvious choice,
due to it being a common factor between Safari and Chrome.

> Also if it was a network stack issue it would be very coincidental that it's on
> both Google Chrome and Safari 4 on Windows and Mac OS. Surely they use
> different network stacks?

It's not all that coincidental when you consider that Google makes use of
Mozilla's data file to define which domains are top-level
(<http://src.chromium.org/viewvc/chrome/trunk/src/net/base/effective_tld_names.dat?revision=3887>).
 I don't know what CFNetwork does, but the license on that file seems open
enough that its possible it too uses rules derived from Mozilla's data file.

Thanks for taking the time to report this bug!


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.