-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Says Browser Is Outdated When It Is Not #525
Comments
This happens in two cases:
In your case it is number 2 and you can find out in your browser debug window network tab and your http daemon logs. |
I see this in
I am checking my browser logs now. |
Browser Log:
|
Right, your:
|
No. The files were there in their entirety, specifically those belonging to 2.18.0. If you yourself were checking my hosting domain which was not indicated to me but I have no problem doing, what you actually saw was that I had cleared things out between the time of posting my log files and now. I was testing a number of options including switching out files from CyberPanel’s build (to see what worked in their earlier build), a Docker image, etc. The only reliable information would have been the logs as that was the only thing requested here. In the future, let me know if you plan on looking at the site yourself so I can keep things static there.
Thanks for adding this to the documentation. |
OK. Compression appears to not be the issue. I first set .htaccess to not use compression:
I second made sure compression was disabled with my virtual host. Neither seems to be the real culprit as I am still getting the bad browser error. The site has been reverted to its original state of 2.18.0 as originally reported so feel free to look at things now there on the domain if you get a notion to. The logging seems to indicate the same issues as before, as well. Browser logs:
Server logs:
|
Somehow something is still screwed up in your configuration. Remove the .htaccess file in Because that file is programmed for Apache and might not work well in LightSpeed. |
Strangely enough, the CyberPanel implementation of 2.15.3 of snappymail uses this as their .htaccess in that path:
|
That worked! Oddly enough, though, CyberPanel does not have to delete that .htaccess file for it to work in their implementation of Snappymail in the web panel environment. I was "checking my work" against that and that was probably what was throwing my scent off of the trail. I can only assume here, but I strongly suspect that it comes down to CyberPanel using LSCPD while the virtual hosts use OpenLiteSpeed. For context, LSCPD (what CyberPanel uses which is a subset of commercial LiteSpeed which has full Apache .htaccess support) probably reads and understands and uses this .htaccess file properly. On the other hand, OpenLiteSpeed (which has "mostly" full Apache .htaccess support with minor changes here and there, like these: https://openlitespeed.org/kb/apache-rewrite-rules-in-openlitespeed/; https://openlitespeed.org/kb/how-to-set-up-custom-headers/) falls short and likely kicks it to the curb. |
Documentation-wise, I think I may found the solution to get OpenLiteSpeed to serve the precompressed JS and CSS content. It would involve a manual modification in the manner of what is shown here within OpenLiteSpeed's web panel: |
I am trying to install SnappyMail, but when I extract it and try to access it from any browser or devices (iOS 16 Safari, Windows 11 Edge or Chrome or Firefox), it says all of my browsers are outdated.
The text was updated successfully, but these errors were encountered: