From Safari 2.0 the login in this page (anche in whole part of the site tim.it except homepage) reload without doing anything. The data are correct, but the page reload identically.
It's not clear to me where the problem is with this site. Submitting the login form with a bogus username/password takes me to a login error page as can be expected. It's not obvious what, if anything, is not behaving correctly.
I'm experiencing this problem too.
When you login with proper username an password and try to access information on popups (traffic details, service state, ...), the website says that the session is expired. Maybe you can tell me how to log what's happening in Safari to send you better information, because I can't disclose my username / password for this website.
This could be a duplicate of Bug 3512. Please log into the site using Firefox and note what domains the cookies are set on. Then log into the site using Safari and see if the same number of cookies are being set.
Optionally, report the "domains" of the cookies being set back in this bug.
(In reply to comment #3)
> This could be a duplicate of Bug 3512. Please log into the site using Firefox
> and note what domains the cookies are set on. Then log into the site using
> Safari and see if the same number of cookies are being set.
> Optionally, report the "domains" of the cookies being set back in this bug.
I didn't see any cookies that had a domain of ".tim.it" or similar, so this probably isn't the problem unless the cookies aren't set until after you log in. Please check to see if any cookies are set after you enter a valid username and password with a domain that looks like ".tim.it".
Another thing to try would have been a packet sniffer like tcpdump or ethereal, but since this is an SSL web site, those won't work. You'll need something like "Charles" to act as a "man-in-the-middle" SSL proxy to capture what is being sent between the web browser and the web server.
Compare the results of Safari to Firefox (or another browser that works), then report back what you find here.
Yes it's definitely a duplicate of that bug.
Looking with Charles as you said, I found that Safari doesn't send some of the cookies it did receive from the server. Firefox sends them correctly.
Sent from server:
HTTP/1.1 302 Moved Temporarily
Date: Sun, 02 Jul 2006 18:05:30 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: COOKIE_IDENT_SERVIZIO=/r...w==; domain=.tim.it; path=/
Set-Cookie: TIM_ID_YACAS=5...d; domain=.tim.it; path=/
Set-Cookie: COOKIE_IDENT=/r...w==; domain=.tim.it; path=/
Set-Cookie: TIM_ID_SYACAS=5...d; domain=.tim.it; path=/; secure
Set-Cookie: CAS_119_UPC=3...a; domain=.tim.it; path=/
Set-Cookie: CAS_UPC=3...a; domain=.tim.it; path=/
Set-Cookie: CAS_SCC=3...3; domain=.tim.it; path=/; secure
Set-Cookie: COOKIE_UNITIM=s...U; domain=.tim.it; path=/
(I added the ... to shorten the message and protect privacy)
GET /selfcare/creditoPrepagato.do HTTP/1.1
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; it; rv:126.96.36.199) Gecko/20060508 Firefox/188.8.131.52
Cookie: vgnvisitor=2...3; COOKIE_IDENT_SERVIZIO=/r...A==; TIM_ID_YACAS=5...d; COOKIE_IDENT=/r...A==; CAS_119_UPC=3...9; CAS_UPC=3...U; CRUSCSESSIONID=G...7
GET /selfcare/creditoPrepagato.do HTTP/1.1
Accept-Encoding: gzip, deflate
Cookie: ARPT=W...O; FSESSIONID=G...59; vgnvisitor=2...e
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; it-it) AppleWebKit/418.8 (KHTML, like Gecko) Safari/419.3
I have to mention that the page where to login is https, the page I try to access in this trial is http.
Hope this helps.
Marking as a duplicate of Bug 3512. At this point, the fix is not in WebKit, but in Foundation classes. A Radar (internal Apple) bug has been opened for issue 3512, but it apparently hasn't been fixed in Mac OS X 10.4.7. (Is that what you're running now?)
It will help to report this issue (again) using https://bugreport.apple.com/. If you don't have an Apple Developer Connection (ADC) account, you can sign up for a free "online" account using http://connect.apple.com/. Please reference this Bugzilla bug, Bug 3512 and the Radar bug mentioned in that report (<rdar://problem/4110617>). It will be marked as a duplicate, but the more duplicates Apple gets for a given report, the better the chances are that it will get fixed.
*** This bug has been marked as a duplicate of 3512 ***