Adding custom headers to cached documents

We will look into setting custom headers. It should work.

To clarify, you are looking to add the ETag header to files that are served from the cache? Or are you looking to add the ETag header to files that are inserted into the cache?

To provide more information, when a page is cached, the headers are also cached (minus set-cookie), so the rules you need may differ depending on what you’re looking for.

I’m not sure what option is more accurate in the validation of the 304 response, but as long as a cached file is valid, it should generates a 304 response, so I think that the option of adding ETag to the files served from cache is better. I’ve been using it with success for a long time through the .htaccess file of the cache storage directory, for example wp-content/cache/page_enhanced from W3TC.

Currently, the cache does not handle the ETag Header. It will be added to LSWS Enterprise 5.1.8.

The cache location will not matter.

Thanks for bringing this issue up!
Kevin

Thanks to you for the consideration.

I’m currently testing LSWS with the free 15 day trial.

Just to be clear; I talked about .htaccess in wp-content/cache/page_enhanced from W3TC, but I’m using LiteSpeed Cache now.

So you will add the rule to the regular wordpress .htaccess, correct?

I tried to add it in the regular WordPress .htaccess using the code above, which is what I was using previously within W3TC cache storage directory, but with LiteSpeed only Cache-Control is added.

Anyway, there is a problem by adding ETags in the regular WordPress .htaccess. I think it would be better if ETags are handle by LiteSpeed Cache module and not in the regular WordPress .htaccess.

Why?

Although I couuld accept adding ETags to all responses, I’m sure many people would want to add ETags only to certain documents types, and that is not always posible in the WordPress root directory. At least I’ve not found a way to do it.

For example, if you use this permalink structure for a post: example.com/some-post, it returns a HTML document but without a html file extension, so you can not use FileMatch. You can not check mime types neither at this moment, as it requires the response and we are earlier.

There can be also a URL that returns a XML document, for example example.com/comments/feed.

In this context, using the root .htaccess you could not add ETags only to HTML documents if you want. At least, again, I’ve not found how to do it.

In other cache plugins using disk for cache storage, this can be solved by using the .htaccess in the storage directory.

That is why I think if you shold be handle by LiteSpeed Cache module. I hope it makes sense.

Understood. Thanks for the clarification. Will get back to you on this.

For what it’s worth, it may be a bit tricky because we do not redirect the request to the cache root. The original path (post rewrites) is used to create the cache entry. Either way, I will get back to you when I have a solid answer.

Kevin

Ok, thank you.

Anyway, adding support for ETags in .htaccess would be great also. Don’t forget that.

I have clarification from both sides ??

So the FileETag rule you listed above does work in Enterprise already. However, as I mentioned before, our cache entries aren’t actual files, so that rule did not work for the requests served from cache.

That said, the thing I mentioned earlier that will be added in 5.1.8 – we will add an option to our configurations that enable admins to select “add ETags to cache entries”. That should take care of your original issue, I think.

Let me know if this answers your questions!
Kevin

`Yes, it does. Everything is perfectly clear.

Thank you!!

Hi Cybmeta,

We released 5.1.8 last week. It should have included the ETag support. Let us know if you encounter any problems!

Tested and working. Thank you!!

Good to hear!

Cheers,
Kevin