You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just putting this here for now, I know this plugin doesn't support it yet.
I would love to see the ability to define either a whitelist or a blacklist of routes that would have the CORS headers enabled on them. If I have some time at some point, is this a feature that you would welcome?
The text was updated successfully, but these errors were encountered:
Thanks for your input. Yes, a black- or whitelisting feature is actually on our wishlist. I think a simple repeater with a "starts with" configuration for urls or some sort of route selector would already do the trick.
On Feb 15, 2017 00:59, "Tobias Kündig" ***@***.***> wrote:
Thanks for your input. Yes, a black- or whitelisting feature is actually
on our wishlist. I think a simple repeater with a "starts with"
configuration for urls or some sort of route selector would already do the
trick.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG6vUIJYUnAcIp7MQwK6Lh4ep1D-JokJks5rcqI0gaJpZM4MBQDC>
.
Just putting this here for now, I know this plugin doesn't support it yet.
I would love to see the ability to define either a whitelist or a blacklist of routes that would have the CORS headers enabled on them. If I have some time at some point, is this a feature that you would welcome?
The text was updated successfully, but these errors were encountered: