I need to know what the --disable-web-security parameter does in chrome. I know that it disables same origin policy.
But I also noticed that it messes with your websockets (I first experienced it with googles gmail, now with my own nodeapp)
So what does it do exactly?
edit:
with messing I mean that I often fail to connect or lose connections to websocket-webapplications (while my chrome runs with the --disable-web-security parameter ). bear in mind that this is only an empirical diagnosis - I am not perfectly sure whether this parameter corelates with my connection issues.
Originheader, nothing in the browser will protect it automatically. I wonder if--disable-web-securityprevents this header from being sent for cross-origin WS connections (I've not tried it)?