Skip to main content
AI Assist is now on Stack Overflow. Start a chat to get instant answers from across the network. Sign up to save and share your chats.

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 1
    and your site has a great example of use with to prerender for all pages. zanon.io/posts/… .- Thank you Commented Jun 1, 2017 at 2:33
  • Does this fourth approach address the user reloading the pushState URL? It handles navigation just fine but on a reload, it will still reach the server. Commented Jun 11, 2017 at 17:24
  • @Alpha, I'm not sure if I have understood your question correctly, but on a reload, it would act as a new request. S3 would receive the request and return the prerendered page again. There is no server in this case. Commented Jun 11, 2017 at 21:17
  • @Zanon Ah, I think I understand. I thought it was meant to cache prerendered pages and avoid going for the S3 unexistent resources. This would leave out routes that have dynamic elements, right? Commented Jun 11, 2017 at 23:34
  • 1
    @Zanon I finally understand -- thanks! Yes, that's what I meant. :) Commented Jun 11, 2017 at 23:46