Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More helpful error response #17

Closed
mattattui opened this issue Mar 6, 2015 · 3 comments
Closed

More helpful error response #17

mattattui opened this issue Mar 6, 2015 · 3 comments

Comments

@mattattui
Copy link

Currently when the policy is violated, only a simple "Not allowed." response is sent. I'd appreciate it if the message was a little more specific, for instance "Access denied by CORS policy". Alternatively, the ability set a custom message or even supply a custom response would be great!

@asm89
Copy link
Owner

asm89 commented Apr 10, 2017

👍 if you want to make this configurable

if (!$this->cors->isActualRequestAllowed($request)) {
return new Response('Not allowed.', 403);
}

@davidbarratt
Copy link
Contributor

davidbarratt commented Apr 4, 2020

I would instead remove the error responses completely. See #65

@barryvdh
Copy link
Collaborator

We've removed the errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants