Bug 12989

Summary: [S60] HMNN-6YNH7J -- Browser: page info not shown correctly after going back to secure page
Product: WebKit Reporter: Yinxiu Cai <yinxiu.cai>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: CLOSED FIXED    
Severity: Normal CC: bradley.morrison
Priority: P2    
Version: 420+   
Hardware: S60 Emulator   
OS: S60 3rd edition   
URL: https://neptune.wipsl.com/wap2.0/entry/secure/secure.xhtml
Attachments:
Description Flags
HMNN-6YNH7J -- Browser: page info not shown correctly after going back to secure page Sachin.Padma: review+

Yinxiu Cai
Reported 2007-03-06 15:48:46 PST
1. Open the page https://neptune.wipsl.com/wap2.0/entry/secure/secure.xhtml (if using NTN SIM card address is: https://10.36.1.12/wap2.0/entry/secure/secure.xhtml) 2. After the page has been loaded, see Options -> Tools -> Page info 3. Then go to e.g. web address www.fi (select Yes for "Leaving a secure web page. Continue?" 4. Go back to the secure page (select Yes for "Opening a secure connection. Content cannot be seen by anyone else." 5. See Options -> Tools -> Page info
Attachments
HMNN-6YNH7J -- Browser: page info not shown correctly after going back to secure page (2.16 KB, patch)
2007-03-07 12:31 PST, Yinxiu Cai 		Sachin.Padma: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Yinxiu Cai
Comment 1 2007-03-07 12:31:26 PST
Created attachment 13522 [details] HMNN-6YNH7J -- Browser: page info not shown correctly after going back to secure page After discussing this issue with UI leader, she said if page is loaded from cache, cert info should be NULL. "Connection info" shown on UI info page should be "non secure". So I am making webkit to address this.
Sachin Padma
Comment 2 2007-03-07 14:30:26 PST
Comment on attachment 13522 [details] HMNN-6YNH7J -- Browser: page info not shown correctly after going back to secure page r=me. For 3.2
Bradley Morrison
Comment 3 2007-03-07 15:25:19 PST
landed - r20035
Bradley Morrison
Comment 4 2008-04-09 11:39:48 PDT
Bulk closing of all s60 platform bugs. Sorry for the noise!
Note You need to log in before you can comment on or make changes to this bug.