Server caches blocks/transactions responses

[mhuggins]

Not sure if this is an issue with the actual HTML response being cached or the graphql results getting stuck in memory somehow. This only happens when the server generates the HTML for either the /blocks or /transactions route, not when it is client rendered (after first hitting the home page, for example).

[mhuggins]

Fixed.

[mhuggins]

Turns out the "network-only" fetchPolicy is not working on the server. The react-apollo code is explicitly changing the value to use "cache-first" for some reason: https://github.com/apollographql/react-apollo/blob/1b28d92cf1a09fe28c40cbad91b31a0208313663/src/graphql.tsx#L417-L422.

See issue here: apollographql/react-apollo#556.

Possible solution is to switch to using the withApollo higher-order component, which would provide the ApolloClient instance. I could then use that to make a request with forceFetch: true maybe. (Can't really find any documentation on forceFetch to support that idea though.)

[mhuggins]

As a workaround, I've set the ssr: false option on all graphql requests. The downside is that the server always renders a loading state instead of providing recent data.

[mhuggins]

Closing this for now since my workaround is working.