- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Since direct requests to API Gateway work, the most likely cause (as you pointed out) is that the header used for auth (presumably Authorization
) isn't reaching API Gateway when your request is proxied through CloudFront.
The article linked in your response should indeed be the fix for this problem, provided you're in fact using the Authorization
header.
Since it didn't work, it would be helpful to see what your current distribution configuration is, especially with regards to the policies or legacy cache settings.
We have tried a variety of configurations based on instructions found via searching. All yield the same results. Our current settings are as follows:
We have also tried using legacy cache policy and adding Authorization there. Happy to give more information.
Contenuto pertinente
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 5 mesi fa