Search results

Hi Mistwang, It took a while before my host was able to upgrade litespeed to 5.2 as they needed to test it out first before rolling out the update. My server has been updated now, and i no longer have the issue with etags. So looks like the update did the trick! Thanks

I am having the exact same issue! Gmetrix is telling me my etags are misconfigured. When using FileETag MTime Size I get the same -0 component. I thought something was wrong and have been struggling to fix it without success for the past few days then found this post. Looks like it is working...

Just spoken to my host about this and they said they are using litespeed server. I found this page which has identified the problem: https://www.litespeedtech.com/docs/webserver/config/tuning#fileETag The question now is how can my host modify the Etag settings to not include the inode component...

Hi, I know this is an old thread but i found it when searching for an issue i'm having with ETags that i'm hoping someone can please help me with? I have used FileETag MTime Size in my htaccess to configure ETags for use with a cdn. This produces ETags with the following format 0-6106-4f5f3bc1...