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
{{ message }}
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
The fourth lab, when setting up preflight headers, tells you to set CORS preflight and change the status code to 200 in the event of an options call. This is really hacky -- if you put any sort of key or header verification in the proxy endpoint then this is only working because the program initially fails. Wouldn't it be safer and smarter to move api key verification, quota limiting, etc to a target endpoint and remove the default fault rule?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The fourth lab, when setting up preflight headers, tells you to set CORS preflight and change the status code to 200 in the event of an options call. This is really hacky -- if you put any sort of key or header verification in the proxy endpoint then this is only working because the program initially fails. Wouldn't it be safer and smarter to move api key verification, quota limiting, etc to a target endpoint and remove the default fault rule?
The text was updated successfully, but these errors were encountered: