Please try FireFox. chrome and FireFox support HTTP/2, IE does not.
If it really is a HTTP/2 compression problem, it will be hard to fix.
We have to find out what exactly happened down the wire.
I am not confident that we could get enough clue to get it fixed without experiment/reproduce the...
Hi, please send you debug log to bug@litespeed... If temp root access is available, we can quickly identify the issue and have it fixed. It is likely an issue related to HTTP/2, 4.2.23 does not have HTTP/2 support. Please contact bug@litespeed .
You need to follow the documentation to enable litemage.
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:cache:litemage
You can host wordpress on the same server. HTTP/2 is faster. recommended.
Yes, it is only one configuration change for LiteSpeed as well, if respecting respond cache control header is all you want.
http://www.litespeedtech.com/docs/webserver/config/cache#cachePolicy:ignoreRespCacheCtrl
set it to "No".
We have not been able to reproduce it with IE 11 in our lab. We have 5.0 Build 9 now, can you try it again. If still not working, we may need to login to your server to investigate if you would like.
Does it happen every time accessing that page? or it is random. We need to get enough information to trouble shoot this, the best way to have it fixed is to reproduce it in our lab. Otherwise, fix cannot make into next release.
Most likely your server was hitting by ip_conntrack limit, do "dmesg" see if you get anything related to that limit. Google on how to increase that limit.
Can you turn on debug logging, and make a request to reproduce the bug, then send the log file to bug@litespeed... ?
we need to know what exactly happened.
Added LiteSpeed staff status to Pong. :)
Does it happen to specific browser, like safari? or all browser has this problem? is HTTP/SPDY in use? or it is just regular HTTP connection?