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
Apologies if this is an obvious or redundant question, I'm very new to Chalice and backend web in general.
I'm trying to connect my website's frontend to my Chalice REST API. My website has two subdomains: "mywebsite.com" and "www.mywebsite.com". I would like to add both of these origins to my CORSConfig for an API route. The documentation states:
You should only supply a single origin to the CORSConfig object. If you need to supply multiple origins you will need to define a custom handler for it that accepts OPTIONS requests and matches the Origin header against a whitelist of origins. If the match is successful then return just their Origin back to them in the Access-Control-Allow-Origin header.
Is there some additional guidance, beyond this doc, on best practices for implementing this? I have no clue what this handler should look like.
The text was updated successfully, but these errors were encountered:
Apologies if this is an obvious or redundant question, I'm very new to Chalice and backend web in general.
I'm trying to connect my website's frontend to my Chalice REST API. My website has two subdomains: "mywebsite.com" and "www.mywebsite.com". I would like to add both of these origins to my CORSConfig for an API route. The documentation states:
Is there some additional guidance, beyond this doc, on best practices for implementing this? I have no clue what this handler should look like.
The text was updated successfully, but these errors were encountered: