[Next 16] Manifest file and robots.txt are encoded

[AyronK]

I've started testing 3.0.0-next16-alpha.2 and spotted a bug that looks to be cache handler related. The Generate a Manifest file implementation of /manifest.webmanifest results in the manifest file response being a base64 encoded string of the manifest JSON. Same is happening with the robots.txt.

EDIT: So this looks to be more nuanced, the first response that gets loaded from the static files on disk is base 64 encoded, once the response comes from the cache, then it is no longer base 64 encoded.

Originally posted by @m-sanders in #110

[m-sanders]

I wasn't previously loading in the generated via the instrumentation.ts but I've updated the code to do this and I no longer end up in this invalid state as the data is now always available via Redis. Seems risky though as we occasionally do flush the cache.

But this makes me think that this isn't related to the cache handler.

[m-sanders]

I've tracked this down to customization of the cache handler we've done to skip caching certain things. Removing the customization resolved the issue. You can close this issue.