- di Slideroh, un anno faValutata 4 su 5Everything worked fine until the last Firefox update. Now it doesn't display - incorrect CORS request. Is this also affected by TLS 1.0 / 1.1, which have been disabled by the browser? Please help us.
Replica dello sviluppatorepubblicato il un anno faI can't magically guess things, you need to report them in a way that I can reproduce.
- di Utente Firefox 13436302, un anno faValutata 4 su 5It does the job and does it very well and simple. But in my opinion lacks some features. I would like to have an option to enable CorsE only on specific domains/websites. This way if I turn on CorsE and start navigating other websites, I'm sure other websites can't mis-use my CorsE being on.
- di Utente Firefox 14504206, 2 anni faValutata 4 su 5what's the difference between 'Force value of "access-control-allow-origin" ' option and 'Activation whitelist' option? I don't understand, i think both are the same, right.
Replica dello sviluppatorepubblicato il 2 anni faThe first option forces the value of the "origin" request header which will also become the value of the "access-control-allow-origin" response header. It's useless for most people and only there for testing purposes.
The whitelist defines which values of "origin" are allowed to bypass CORS when the addon is active. It's a list of fully qualified regular expressions, with delimiters and flags, separated by newlines.
See also this: https://github.com/spenibus/cors-everywhere-firefox-addon/issues/23#issuecomment-447669576