But I have hopes of a knife option. Does that change your thinking on this? As you can see on the screenshot above, Chrome lists the location the plugin is installed on the system. You should be able to do this; something similar to the aforementioned add-on ought to work fine. I am a developer, but in this case, that has no bearing. Stability and security will suffer. Imagine you are making a Desktop App that uses Gecko View. We'd like to find something more fine-grained that solves the problem without the dangerous downsides.
To my mind, making this permanent is more problematic. For Windows users: The problem with the solution accepted here, in my opinion is that if you already have Chrome open and try to run this it won't work. For all other browsing, I use the default firefox build of my distro. You have two options here: 1. Might be evaluating an evil script! While the default policy doesn't restrict connections to hosts, be careful when explicitly adding either the connect-src or default-src directives.
The —disable-web-security is no longer supported in recent chrome versions. Note that there could still be scenarios where these tricks fail to work. If possible, I'd really rather not do any of that, and instead just be able to double-click on the index. Oh, some server thing - not my problem, I don't touch the server, ignore. As Jeff Griffiths mentioned, you would have to checkout the mozilla source code, apply that patch and rebuild firefox from the patched source.
However you can just ignore that message while developing. As has been mentioned in the comments, it may be better to adjust or even intercept and change via proxy, if you have to the headers on the appropriate pages. It's just a fluff type thing. Requesting cross-origin permissions By adding hosts or host match patterns or both to the section of the file, the extension can request access to remote servers outside of its origin. Only this much: with click to play plugins that are activated in Chrome do not get loaded when you load a website in the browser. As it so often happens, I've found an answer almost as soon as I've gone to ask for help. Stability and security will suffer.
I'd rather not have to. Instead run a local server. Please help me with this issue! I liked the Firefox developer edition. In order to use that patch, you would need to apply it to a checkout of mozilla-central and then create your own build. The second however needs some explanation. The switch can not be hidden while it is enabled. Mentioning this user story, I am wondering how the devtools-open requirement works so well for this kind of automated testing.
One-man shops and elite do-it-all-yourself programmers falsely assume that every person, just like they themselves are, would be in control of everything and be knowledgeable about everything involved in the development of that software system. Once you do this any 3rd party site can start issuing requests to other websites, sites that you are logged into. Not perfect, but it works okay. Naturally having better prints is always helpful, but that alone doesn't solve this, since sometimes you don't have login to the server you are developing against, or the server guys are in different timezone and it's night there, or it's someone else's job and you are not allowed to change the server code anyways. If you chuckled on the previous point, then it's not just a good and reasonable integration testing practice, it's simply required.
On Windows 10, right-click on the Chrome icon, then right-click on Google Chrome, then click Properties. I assume this is because they do not have their servers configured correctly. Also note that access is granted both by host and by scheme. Developers will need to develop and need to be able to have workarounds when they face errors they cannot resolve themselves. Start up a small server There could be a scenario where your requests are still giving you a hard time. Uninstalling and reinstalling the extension fixed it to reset the defaults. Used by people testing their sites.
In the Develop menu make sure that Disable Local File Restrictions is checked. I am not even speaking about adding it to main build, I am requesting it to be added not the patch if it doesnt do that, the feature to Firefox Developer Edition. In the Target field, append the launch flags. Flag stays put and activated until you go back into options and turn it off again. Instead, design message handlers that limit the resources that can be fetched. Update: For Chrome 22+ you will be presented with an error message that says: You are using an unsupported command-line flag: —disable-web-security. The chosen answer is good, but for those who are still struggling with what they are talking about your first time dealing with this issue , the following worked for me.