-
Notifications
You must be signed in to change notification settings - Fork 2
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
add test for non existing document to see if CORS is correct #26
Comments
Wait, was it a 500? Then the non-existing doc (which is tested I believe) would be a random thing to test for, if what you actually want is trigger a 500. |
No, it was a 404. I guess it doesn't make that much sense actually to test this since a 404 is 'expected behavior'. It is just that in my implementation they follow a different program flow for which I initially forgot to add CORS. That is fixed now, so it can't happen anymore, but I thought other implementation may be similar in having a different flow for 'failures'. |
We should totally add a test for 404s then. Very easy. |
What if we checked the CORS headers inside |
Yes, makes sense I assume. |
My code has a different flow for exceptions (i.e. file does not exist) and the exceptions didn't add CORS headers...
The text was updated successfully, but these errors were encountered: