brett.tasker

The 2nd option (self-hosted) allows the client to control access to this content directly (e.g. they can remove the file from the system after confirmation from HD that they have a copy).

However this also depends on the tooling available to you. Sometimes Password protected + 2FA SMS can be best option as it doesn't require any 3rd party service.

brett.tasker

Otherwise

• Self-hosted (e.g. google drive) and ask for email to share it with.

brett.tasker

Password protected ZIP file containing a TXT file with Key. (Upload to HD) Then you can ask HD for a SMS / TXT number to send the password to (2FA)

brett.tasker

I haven't had a chance to test CGI vs FPM so far, but FPM vs mod_php.... FPM is way better.

👍 (1)
brett.tasker

I would recommend using either Apache + PHP-fpm / CGI OR nginx + fpm / cgi.

Gone are the days where 3 layers are needed and all it does is add additional layers of complexity which are often not required.

brett.tasker

The fact that your "Include" works but the Layout is not makes me thing that perhaps you have your layout page.ss in the wrong folder location.

brett.tasker

If you just use renderWith('Page') does that show your layout correctly?

brett.tasker

What caching headers are you seeing on these pages? (E.g. Cache-Control). It's possibly that this is not a HTTP cache issue, but an internal cache issue (E.g. Partial caching) which may be causing this.

taoceanz

In Request headers:

  1. Cache-Control: no-cache
  2. Connection: keep-alive
  3. Pragma: no-cache
taoceanz

Ah, found this in NGINX configs:

  1. fastcgi_ignore_headers Cache-Control Expires Set-Cookie;
  2. server {
  3. listen 80;
  4. server_name http://something.com;
  5. .
  6. .
  7. .
  8. expires 2w;
  9. }
brett.tasker

What about response headers? (They are the ones that matter usually when telling if cached)

taoceanz

Hey @brett.tasker yes sorry I'd started writing the return headers but got distracted investigating the issue.

With fastcgi_ignore_headers and expires 2w set, the response headers show it was caching in admin and on front-end. I'll need to reconfigure so it's caching the assets on the front-end and not just caching absolutely everything to do with the website.

👍 (1)