Take IsolatedCopy() before registering isolated world's SecurityOrigin
XMLHttpRequest's responseXML's SecurityOrigin is aliased with its ExecutionContext, i.e. either with Document or an isolated world, in XMLHttpRequest::InitResponseDocument(). This CL is a preparation for making SecurityContext::GetSecurityOrigin() and XMLHttpRequest::GetSecurityOrigin() return const SecurityOrigin* in [1], while preserving the aliasing behavior in XHR. [1] https://chromium-review.googlesource.com/744586 This CL - Introduces XMLHttpRequest::GetMutableSecurityOrigin(), - Uses ExecutionContext::GetMutableSecurityOrigin() for aliasing with another Document and - Uses the registered SecurityOrigin of an isolated world in DOMWrapperWorld for aliasing with the isolated world. This CL Takes IsolatedCopy() before DOMWrapperWorld::SetIsolatedWorldSecurityOrigin() in WebLocalFrameImpl::SetIsolatedWorldSecurityOrigin(), to make SecurityOrigin inside its argument (WebSecurityOrigin) const. This IsolatedCopy() doesn't cause semantic changes, because the callers of SetIsolatedWorldSecurityOrigin() never pass an aliased WebSecurityOrigin. Bug: 779730 Change-Id: I503c0623f15e37cba010a0c7f0b72e2b44f5af08 Reviewed-on: https://chromium-review.googlesource.com/752006 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:Takeshi Yoshino <tyoshino@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#521260}
Showing
Please register or sign in to comment