Hi @sarasri ,
I visited your sitemap URL and the response headers are:
age: 5
cache-control: maxage=31536000
cf-cache-status: HIT
cf-ray: 6119381f9d89f917-MXP
cf-request-id: 07a3a167bf0000f917762a7000000001
content-encoding: br
content-type: text/xml; charset=UTF-8
date: Thu, 14 Jan 2021 17:53:55 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Fri, 14 Jan 2022 17:53:49 GMT
nel: {"report_to":"cf-nel","max_age":604800}
pragma: public
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=%2FkLlElF2kSopeujcMbcX3CumMjf2%2FRMRMG9pJPXYFcXg34K%2FWX1NxSVVWaLgCbdLRk9qqdQCjfMDNpCCrMDr2GdNGOBHG4TZok8R81mG"}],"group":"cf-nel","max_age":604800}
server: cloudflare
vary: Accept-Encoding
x-powered-by: PHP/7.4.11
x-robots-tag: noindex
x-turbo-charged-by: LiteSpeed
x-wp-cf-super-cache: no-cache
x-wp-cf-super-cache-cache-control: no-store, no-cache, must-revalidate, max-age=0
As you can see, the x-wp-cf-super-cache-cache-control is set to no-cache but there is a different cache-control.
So another plugin (or server rule) is adding this cache-control, it’s not a plugin issue.
Please check your Litespeed server browser caching rules