simply_static_page issues

Viewing 1 replies (of 1 total)
  • Plugin Author patrickposner

    (@patrickposner)

    Hey @fliespl,

    thanks for your suggestion!

    We used the URL parameter instead of a custom header for a couple of reasons:

    Cache Busting:

    A significant portion of our user base uses shared hosting plans, and what’s even worse is that they use Litespeed instead of Apache/NGINX.

    The problem is that you can’t bypass the cache with a custom header here, which has resulted in hundreds of complaints that the static site isn’t updating at all.

    The URL parameter solves as a mechanism to prevent that.

    Wrong usage of Custom Headers:

    We noticed that many plugins use custom headers for things like license validation, but most of them simply overwrite the existing headers passed via the http_request_args filter we are using internally.

    That’s why we opted to use the query string instead of custom headers.

    However, I could see this being offered as an alternative via filter.

    Our development is happening publicly on GitHub, so feel free to provide a PR with your suggested changes, and we will review and merge it: https://github.com/Simply-Static/simply-static

    Cheers,
    Patrick

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.