Lambda@Edge to configure SPA client side routing? (ReactJS) S3 + CloudFront

My website is a static site in S3 and I'm using CloudFront. Since it is a SPA , the origin returns a 404 error on every request but loads the page successfully. To solve this I have created a custom error in "Error page" in CloudFront so that it returns a status 200. (This is what is recommended in most blogs) This works fine but on every html request I see cache: "Error from CloudFront".

My question is if CloudFront is caching the request or is it always going to the origin? Would it be better to handle this with a Lambda@Edge? How?

Thanks in advance!

주제

네트워킹 및 콘텐츠 전송

태그

아마존 CloudFront

언어

English

Gabym

질문됨 9달 전228회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

Hi,

When you configure the custom error page there is TTL Enter image description here

About the Lambda@Edge, at least it will cost you additional money for something that is free now.

전문가

Dmytro Sirant

답변함 9달 전

전문가

Didier_Durand

검토됨 9달 전

Gabym
9달 전
Hi Dmytro, Thanks for yor answer. What time(seconds) is recommend for TTL?
Dmytro Sirant 전문가
9달 전
It's hard to say without knowing how dynamic your content is. You may find more information by the link https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/HTTPStatusCodes.html

Lambda@Edge to configure SPA client side routing? (ReactJS) S3 + CloudFront

관련 콘텐츠