Serve Static Assets w/ Efficient Cache Policy

Thanks for the message, and it looks straightforward, but I can’t access the WebAdmin. I’m using LiteSpeed w/ Runcloud and Vultr. Here’s what I did so far:

– I created a rich rule in Runcloud to accept my ip on the 7080 port
– I received “Your Connection is not Private” error
– I changed HSTS to allow http and then I got 404 error.

I changed these settings back since I’m not sure if those were correct.

Thanks for the message. I did contact RunCloud and they set it up which resolved the Pagespeed messages for the most part. (One plugin still had messages but I’ll address that later.) Now I’m having an issue where wp-admin seems like it may be caching. Updates sometimes reappear, plugins reactivate, etc. Here is the thread of what they did:

https://manage.runcloud.io/support/tickets/55952

Did they miss this part and could that be causing it?
exp:^.*(css|gif|ico|jpeg|jpg|js|png|webp|woff|woff2|fon|fot|ttf)$

Or is there something else that could be causing it? I think I saw some questions about object cache and I do have object cache on if that is important.

I did, but I wasn’t clear on where to go. I used a Firefox tab that wasn’t logged in. Then I did log in and found this:

cache-control: public, max-age=15552000
content-encoding: gzip
content-length: 27351
content-type: text/html; charset=UTF-8
date: Thu, 05 Aug 2021 20:51:41 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT`

Then further down:

x-litespeed-cache-control: no-cache

I think that means it’s not coming from the plug-in, but is being cached. That’s why I’m wondering if it came from the LiteSpeed Config that RunCloud did in the prior thread. It looks like the custom header page, and here is what they input in LiteSpeed Config:

unset Cache-control
set Cache-control public, max-age=15552000
set Access-Control-Allow-Origin: *

   END_extraHeaders

Thanks for your help so far!

access-control-allow-origin: *
alt-svc: h3-34=”:443″; ma=2592000, h3-29=”:443″; ma=2592000, h3-Q050=”:443″; ma=2592000, h3-Q046=”:443″; ma=2592000, h3-Q043=”:443″; ma=2592000, quic=”:443″; ma=2592000; v=”43,46″
cache-control: public, max-age=15552000
content-encoding: gzip
content-type: text/html; charset=UTF-8
date: Thu, 05 Aug 2021 21:12:42 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT
referrer-policy: strict-origin-when-cross-origin
server: LiteSpeed
strict-transport-security: max-age=15552000
vary: Accept-Encoding
X-Firefox-Spdy: h2
x-frame-options: SAMEORIGIN
x-litespeed-cache-control: no-cache

Thanks qtwrk, so that did update it to 15552001. So this is coming from the code that RunCloud put in trying to address this: https://openlitespeed.org/kb/how-to-set-up-custom-headers/

Is there different code that I need for custom headers? Here is the last part of my OpenLiteSpeed Config. (I just lengthened the expiresByType.)

expires {
  enableExpires           1
  expiresByType          text/css=A15552000, image/gif=A15552000, image/x-icon=A15552000, image/jpeg=A15552000, application/x-javascript=A15552000, text/javascript=A15552000, application/javascript=A15552000, image/png=A15552000, image/webp=A15552000, font/ttf=A15552000, font/woff=A15552000, font/woff2=A15552000, application/x-font-ttf=A15552000, application/x-font-woff=A15552000, application/font-woff=A15552000, application/font-woff2=A15552000
}
context / {

  extraHeaders            <<<END_extraHeaders
unset Cache-control
set Cache-control public, max-age=15552001
set Access-Control-Allow-Origin: *

   END_extraHeaders
}

Yes the header did change. I figured that was probably the issue. I’ll contact RunCloud again and see if they have a suggestion unless you have any additional info on where that should be.