8

I'm wondering, in IE & Firefox you're able to setup the browser, to allow cross-domain calls.

I can't find any option in chrome for that (actually, there are in general not too much options at all...)

are there any about:config like things?

Kind Regards

--Andy

Jesper Fyhr Knudsen
  • 7,802
  • 2
  • 35
  • 46
jAndy
  • 231,737
  • 57
  • 305
  • 359

3 Answers3

21

This answer was correct when written, but is longer correct, the switch has been deprecated

Chrome has a command line switch for this:

chrome.exe --disable-web-security

You can view a full list (as of when it was posted!) of command line options for chrome here.

Anders Abel
  • 67,989
  • 17
  • 150
  • 217
Ashish Agarwal
  • 6,215
  • 12
  • 58
  • 91
  • how to do this programatically? – stackunderflow Nov 08 '12 at 08:26
  • I am not 100% sure but Pragmatically its not possible. logically, by writing above line inside chrome we are disabling a security feature. The feature is only for disabling the particular actions occurring from programming side. That's the reason I strongly believe. pragmatically its not possible. – Ashish Agarwal Nov 08 '12 at 18:24
  • 5
    This option has been removed from Google Chrome, it is only available with Chrome version 21. – Octavian Helm Nov 20 '12 at 08:51
  • 2
    @OctavianDamiean It's still available on Chromium ~25, if needed. – fncomp Apr 08 '13 at 20:21
  • This works perfectly fine in Chrome 37 OS X --> open "Google Chrome.app" --args --disable-web-security – Aaron Sep 19 '14 at 00:23
5

No. Sorry.

Chrome and Firefox, however do support cross-domain requests via the W3C CORS spec (Cross Origin resource sharing) however the remote host has to enable it. If the remote host supports it explicitly then you don't have to make any changes to your XMLHttpRequest to be able to fetch the content.

Kinlan
  • 16,315
  • 5
  • 56
  • 88
2

You can install chrome plugins which enable cross-origin resource sharing .

I use this .

jiahut
  • 1,451
  • 15
  • 14
  • Thanks, I used all the other methods and they worked for awhile but the latest version of Chrome seems to block them. this works. – sigmapi13 Mar 28 '16 at 13:00