Cache problem

[palb]

I have this really annoying problem with page cache. I've done changes in a file, and upload it. But it doesn't show up on the sever side. I've tried to empty cache, but still the same old page. Must be something Litespeed does. The question is what?

---

Now it changed. Seems to come after a while. How can I change this. Very annoying when developing.

[mistwang]

Is it a text file? Maybe it is the gzip cache, you can turn off gzip compression if you can.

Or, you can remove the gzip cache directory.

[palb]

Originally Posted by mistwang

Is it a text file? Maybe it is the gzip cache, you can turn off gzip compression if you can.

Or, you can remove the gzip cache directory.

It's a .rhtml in views. I'll take a look at gzip. Thanks

[mistwang]

does LSWS serve .rhtml directly? or served by rails internally? if it is the later. it must be rails problem, maybe Rails' cache.

[palb]

Originally Posted by mistwang

does LSWS serve .rhtml directly? or served by rails internally? if it is the later. it must be rails problem, maybe Rails' cache.

It's via rails. Thanks for the clarification.

[palb]

The problem is still there and rather annoying. Must be LS issue.

[mistwang]

Whether it is a LS issue or not depends on whether the request being forwarded to rails, or LSWS serve it by itself, or the browser cache it.

You should check rails log and LSWS access log.

[palb]

Originally Posted by mistwang

Whether it is a LS issue or not depends on whether the request being forwarded to rails, or LSWS serve it by itself, or the browser cache it.

You should check rails log and LSWS access log.

All I know is that there is no gzip and rails is in developer mode. It's not a browser cache issue, I know that when I see it.

[mistwang]

If a request go though Rails, LSWS is just a messenger, so check the development.log see if the request hit rails.

[palb]

Originally Posted by mistwang

If a request go though Rails, LSWS is just a messenger, so check the development.log see if the request hit rails.

But LS could still be a messenger that delays the message, or? I mean, what about the ability to do a graceful restart the LS-way. How does that work if not LS has some power over the output and cache.