3 ms·
Sorry if it is not clear, I was referring to html files returned by servers when user visits old-fashioned server-rendered web pages (non-SPA pages) like `/page
by paraditedc 8y ago
Sorry if it is not clear, I was referring to html files returned by servers when user visits old-fashioned server-rendered web pages (non-SPA pages) like `/page1` or `/page2`.
How do you version urls like those?
Something like `/page1?t=201811292359`? That seems ugly to the users.
- gondo 8y agorules i use: - content under certain url should never change - if it has to change then use ESI or/and smaller cache expiration times - if it has to change very often/realtime, then use static html as skeleton and load only required information via javascript. f.e.: info about currently signed in user, eshop basket