interferes with some websites

[tarranjones]

I've had a couple of issues when "Access-Control-Expose-Headers" is enabled and were immediately fixed when disabled.

[tarranjones]

attempting to login to github

[tarranjones]

Playing videos on youtube

[aziz]

That's why I suggest to be able to disable or enable it based on domain, just like how Ad blockers behave.

[tarranjones]

Cant you use localStorage to remember whether it was enabled or not.
Every now and then i use chrome and its enabled again. not sure why?

[yaring]

@aziz sounds great!
You literally cannot use the chrome when having CORS, we definitely needs white list domain based to turn on CORS.

[ondratra]

The problem with websites is that extension thrashes rest of headers(reasons are not clear to me). Lines in background.js:

return {requestHeaders: details.requestHeaders}; ... return {responseHeaders: details.responseHeaders};
should be simply return requestHeaders; & return responseHeaders; (I checked Youtube after this modification and it worked).
@vitvad is there any reason for this?

[ondratra]

Nevermind my previous comment. It actually breaks the mechanism and "working Youtube" is probably just side effect.