Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Allow outer context to access arbitrary URLs #11217

Closed
cburgmer opened this issue Apr 9, 2013 · 2 comments
Closed

Allow outer context to access arbitrary URLs #11217

cburgmer opened this issue Apr 9, 2013 · 2 comments
Assignees

Comments

@cburgmer
Copy link
Contributor

cburgmer commented Apr 9, 2013

Accessing arbitrary domains from PhantomJS' outer context is currently only possible through a dirty workaround (e.g. https://gist.github.com/cburgmer/5339864). For sandboxed webpages this is however easily doable by passing --web-security=no to phantom on the console.

I believe that the outer context should be able to access any resources without restrictions, similar to e.g. Node.js.

Relevant discussion in the phantomjs group: https://groups.google.com/forum/#!topic/phantomjs/Kb06DuqIoxw

@ghost ghost assigned vitallium Apr 9, 2013
@JamesMGreene
Copy link
Collaborator

@vitallium and I are looking into this.

vitallium added a commit to vitallium/phantomjs that referenced this issue Jun 15, 2014
To grant universal access to a web page
attribute "WebSecurityEnabled" must be applied during the initializing
security context for Document instance. Setting up it later will not cause any effect
See <qt\src\3rdparty\webkit\Source\WebCore\dom\Document.cpp:4468>

Issue: ariya#11217
@vitallium
Copy link
Collaborator

Fixed in d938edd

vitallium added a commit to vitallium/phantomjs that referenced this issue May 23, 2015
To grant universal access to a web page
attribute "WebSecurityEnabled" must be applied during the initializing
security context for Document instance. Setting up it later will not cause any effect
See <qt\src\3rdparty\webkit\Source\WebCore\dom\Document.cpp:4468>

Issue: ariya#11217
vitallium added a commit to vitallium/phantomjs that referenced this issue May 31, 2015
To grant universal access to a web page
attribute "WebSecurityEnabled" must be applied during the initializing
security context for Document instance. Setting up it later will not cause any effect
See <qt\src\3rdparty\webkit\Source\WebCore\dom\Document.cpp:4468>

Issue: ariya#11217
vitallium added a commit that referenced this issue Jun 27, 2015
To grant universal access to a web page
attribute "WebSecurityEnabled" must be applied during the initializing
security context for Document instance. Setting up it later will not cause any effect
See <qt\src\3rdparty\webkit\Source\WebCore\dom\Document.cpp:4468>

Issue: #11217
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants