Thanks for the fast reply.
>1. The static content - jpg, png, tiff, etc. It looks as though you are
serving them your backend and caching them. Are they also being built on
demand dynamically? If not, then why csche them? Why not deploy them to
nginx and serve them directly?
There is a huge part
Your question raises so many other questions:
1. The static content - jpg, png, tiff, etc. It looks as though you are serving
them your backend and caching them. Are they also being built on demand
dynamically? If not, then why csche them? Why not deploy them to nginx and
serve them directly?
Hello guys,
I'm having a hard time defining a proxy cache because my landing page
doesn't generate any HTML which can be cached. Quit complicated to explain,
let me show you some logs and curl requests:
curl:
curl -I https://info/de
HTTP/1.1 200 OK
Server: nginx
Date: Thu, 21 Jun 2018 11:56:
