Separate names with a comma.
Discussion in 'Bug Reports' started by cmeinck, Jun 14, 2013.
Credentials have been PM'd to the both of you. Thank you.
when litespeed running on port 2080, no problem at all;
when running on port 80, looks able to reproduce the issue easily, especially on chrome.
it should be a different issue with opencart one which mentioned in this thread.
We're still investigating it.
Thanks Mike to provide us the credentials.
p.s., suspect such request
cause the issue.
can you configure XenForo to disable this feature? let litespeed serve the inidividual .css file directly. see if the issue gone after this change. if this is true, it can narrow the scope greatly.
I think your issue is more likely that PHP randomly crashed in the middle of processing css.php script.
And CDN is used for one of CSS group, so if CDN cache a bad copy, it could many people receive bad CSS.
Right now, litespeed seems stable on port 80.
As far as I know, this cannot be disabled.
Interesting that PHP does not randomly crash in Apache.
As far as being stable on port 80, here are some links:
As far as it being stable, sure, it is stable in the fact that it serves pages lacking CSS around 40% of the time without totally crash dumping. I am surprised you have not attempted to contact XenForo developers to look at this. There is no way I will continue to upgrade the license for this software, or even use it, if this is not considered a serious problem for your software.
It does not occur with nginx, lighthttp, apache, or any other web server.
I am not sure what css problem to look at. thought it is the main layout, appear to be detail in the page. I will investigate more. May need to switch to LiteSpeed temporarily during investigation.
The missing style is from
latest 4.2.4 should have take care of it. I have switched to LiteSpeed and browse the forum for a while with firefox and chrome. not missing style noticed.
Can you please try and let us know how to easily reproduce it?
Sounds like you need to buy a license to continue your investigation now. Please discontinue accessing my server. You are directly damaging incoming traffic to my site with your tests.