Bug 21021 - Session cookies are not send back to server - regression to Safari 3.1 (525.x)
Summary: Session cookies are not send back to server - regression to Safari 3.1 (525.x)
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Critical
Assignee: Nobody
URL:
Keywords: InRadar, Regression
Depends on:
Blocks:
 
Reported: 2008-09-23 02:02 PDT by Thorsten Dencker
Modified: 2008-09-24 01:12 PDT (History)
2 users (show)

See Also:


Attachments
Cookie test file for J2EE engine (e.g. tomcat) (3.13 KB, application/x-zip-compressed)
2008-09-23 02:04 PDT, Thorsten Dencker
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Dencker 2008-09-23 02:02:07 PDT
Hello,

we found a regression in 528.1.1 on windows (Safari 4) in the cookie handling. It works fine with 525.x (Safari 3). I did not test it on MAC yet.

Our session cookie isn't send back to the server if only the host name is admitted in the url. 
* If you start the application with http://mycomputer:1080/myappl the cookie isn't send back to the server. 
* If you use a full qualified name like http://mycomputer.apple.com:1080/myappl it works fine.

This bug is very critical because in normal intranet scenarios you are not using full qualified domain names.

You find a small example in the attachment. Deploy it to a J2EE engine e.g. tomcat, start it with full qualified and non qualified address, press the button and check if the session id appears. 

For easier tracking our internal bug number is 0003634917 2008

Regards Thorsten
Comment 1 Thorsten Dencker 2008-09-23 02:04:37 PDT
Created attachment 23697 [details]
Cookie test file for J2EE engine (e.g. tomcat)
Comment 2 Alexey Proskuryakov 2008-09-23 08:39:06 PDT
This bug is likely to be in closed source Apple frameworks, because cookie handling is implemented there. I can move the bug to bugreport.apple.com for you if you wish, but Apple engineers working on it won't be able to get back to you unless you file it there yourself.

Please let us know if you do this, and post the Apple bug ID here (a seven digit number).
Comment 3 Thorsten Dencker 2008-09-24 00:38:32 PDT
I create a bug report at Apple for this issue - ID# 6242288
Thorsten
Comment 4 Alexey Proskuryakov 2008-09-24 01:12:44 PDT
Thank you!

Now closing as INVALID per our process, as this is unlikely to be a bug in open source WebKit. It will be investigated internally by Apple engineers.