Search results

In you script, just send back response header "X-LiteSpeed-Location: <URL_of_static_file_to_send_to_client>" instead of stream the that file.

Would be very interested in that information, that will be certainly on top of our to-do list to improve our product if it is really true.

All http/2 drafts are out-dated. no matter 14 or 17. We support official http/2 spec. Their test result is not accurate. h2-14 is for backward compatible with client does not support final http/2 spec yet. but most clients has been updated to use HTTP/2 official.

Make sure you have TLSv1.2 enabled, and the cipher need to be started with "ECDHE-RSA-AES128-GCM-SHA256" .

you mean this: https://xenforo.com/community/resources/xenforo-litespeed-cache.2704/

I tried from Mac OS X chrome, also working fine. Anyway, I updated our server installation to 5.0.3 build 2. Please try again. If the problem persists, it could be something to do with your cookie.

Probably not, xenforo should not be affected. I have google chrome Version 44.0.2403.89 m, forum just load fine. Which version of chrome are you using.

RequestHeader operation is not support by LiteSpeed. HTTPS is not a real request header, maybe added by webserver for https connections. In litespeed, it was added as a request environment. Since HTTPS was added by chrome as request header, we may need to get rid of the header with a new build...

It is a bug in LSWS 5.0 regarding Chunked Transfer-Encoding. It is fixed in latest build 5.0.3 . Just tell your host provider to update with command /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.3

Your android client uses "Transfer-Encoding: chunked" for request body, litespeed should be able to handle it. I will double check the latest 5.0.x release, if it is due to a regression in 5.0 release. we will fix it.

Please force reinstall 5.0.2, if it is not fixed, please send us the rewrite rules. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.2

It only crash once, and does not create a core dump, so we could not figure anything out of it. No need to downgrade as it does not happen frequently.

You need to restart the server from command line, logout then log back in to webadmin, it should fix the problem.

something wrong with the IP address.

Yes, it is a bug, we may need temp root access to investigate. Please contact bug@litespeed...

That's due to a change of expected name of proxy target. Will make it compatible with old in next build. Right now, it is preferred to have "http://" or "https://" prefix for name of a web server external application.

We may put out one more release 4.2.x branch if serious security bug has been discovered. 5.x branch will have lot more great features to come, no reason to stay with 4.2.x .

please try command line /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.1

Which OS are you using? 5.0.x packages are available for Linux and FreeBSD. FreeBSD packages now require FreeBSD 8.0+, may need manual download and installation due to package name change.

How about