Status: Started Owner: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend
New issue 4792 by [EMAIL PROTECTED]: Use same SiteInstance for pages from different ports http://code.google.com/p/chromium/issues/detail?id=4792 What steps will reproduce the problem? 1. Visit a page. 2. In same browsing instance (e.g., tab), visit a page from the same domain and protocol, but served from a different port. 3. What is the expected output? What do you see instead? The new page should belong to the same SiteInstance (and be rendered in the same process) as the old page. Currently, Chromium creates a new SiteInstance for the new page because the port is different. Adam Barth points out that two pages from the same domain and protocol can still access each other's contents, even if they are served from different ports. In other words, if two pages change their document.domain variables to match, any difference in the page's ports is then ignored by the Same Origin Policy. There's no major problems caused by this currently because we're pretty conservative about when we switch renderer processes, but we should fix it. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
