Bug 21574 - Cookie handling with Uppercase hostnames
Summary: Cookie handling with Uppercase hostnames
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Major
Assignee: Nobody
URL: http://www.Yahoo.com
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2008-10-13 12:18 PDT by David Alley
Modified: 2008-10-16 23:49 PDT (History)
1 user (show)

See Also:


Attachments
HTML Test Page (229 bytes, text/html)
2008-10-13 12:31 PDT, David Alley
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Alley 2008-10-13 12:18:47 PDT
When following a link that references an uppercase url no cookies are set.  As an example load www.yahoo.com and notice the cookies that are set.  Now create a small html page that has a link to http://www.Yahoo.com and notice that no cookies are set.

This is a pretty big problem because a site will assume that the cookie was set correctly and probably depends on it somewhat.

This can be seen in multiple sites.  I also noticed that when you type a url it is automatically lowercased, but when you following the links they are not lowercased.



<html>
<head>
<title>Cookie handling with Uppercase hostnames</title>
</head>
<body>
<a href="http://www.yahoo.com">Yahoo with all lowercase</a><br/>
<a href="http://www.Yahoo.com">Yahoo with a capital Y</a>
</body>
</html>
Comment 1 David Alley 2008-10-13 12:31:32 PDT
Created attachment 24321 [details]
HTML Test Page

HTML test page with both a lowercase only link and a mixed case link.
Comment 2 David Alley 2008-10-13 12:46:44 PDT
It now looks like when you follow a link with mixed case, if the site issues the cookie with the domain set to the same mixed case then safari ignores the cookie.  I assume that safari is expecting a cookie with the domain set to all lowercase.
Comment 3 Alexey Proskuryakov 2008-10-16 00:49:11 PDT
<rdar://problem/6296293>
Comment 4 David Alley 2008-10-16 15:50:14 PDT
(In reply to comment #3)

Is this scheduled for a release anytime soon?
Comment 5 Alexey Proskuryakov 2008-10-16 23:49:01 PDT
This issue is not in WebKit, but in closed source Apple frameworks it uses. It will be tracked and investigated by Apple internally, closing as INVALID per our process.

You can get information about the progress on this issue by e-mailing devbugs@apple.com and citing the bug number, <rdar://problem/6296293>. Thank you for reporting it!