I'm working on development of a HTML5 web application that requires accessing resources from other domains through AJAX. On Chrome browser, there is a nice way to disable web security and allow cross-domain access for AJAX. However, when it comes to Firefox, there isn't an answer that I found. I'm sure this questions might have been asked a multiple times in various forums. But, does Firefox provide a way to disable this security feature and enable cross-domain access?
Product information: I'm running the latest Firefox on Windows 7 box.
- All posts
- Helpful Solutions
The same-origin policy is an important security protection for browser users. It's what prevents third party sites from reading your traffic, vacuuming up your cookies, manipulating an open page from an iframe, and taking action on your behalf by hijacking your session. I assume that when you disable the same-origin policy in Google that you do not visit any sites you and your company do not personally control. More info: Same Origin Policy Part 1: No Peeking - IEInternals - Site Home - MSDN Blogs.
The official solution is to use Cross-Origin Resource Sharing in the app: https://developer.mozilla.org/en-US/d.../Access_control_CORS. If you have difficulty implementing this, you can get some assistance on the mozillaZine Web Development / Standards Evangelism forum.
We know that. I don't want to keep it on, just turn it on while testing locally to a remote API. I don't want to allow localhost on my server!
Hi oscargodson, yes, localhost sounds like a really bad idea. However, you might be able to edit your configuration file to add an "unguessable" server name with the same root as your localhost instance. Just a thought, I've never tried it myself.
- IMPORTANT ANNOUNCEMENT: We’re going through some system changes, that may have slowed responses to your questions. If you had asked a question in the last couple of months, please re-post it and the community will help you as soon as we can. If you’ve registered after February 7th, please register again, the accounts on the previous site were not migrated to this temporary site. If you joined us before February 7, please reset your password if you have trouble logging into this temporary site.