Project

General

Profile

Actions

Bug #3088

closed

Chrome browser loads slowly with lighttpd 1.4.54

Added by mohan1044 almost 3 years ago. Updated almost 3 years ago.

Status:
Invalid
Priority:
Low
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:
Yes

Description

We are using chrome version 91.0 and Lighttpd 1.4.54 to access specific Access point. we are facing the issue of slowness in the chrome browser in the specific lighttpd version(1.4.54). we are not facing any issue in 1.4.45. We could see from release notes that "In lighttpd version 1.4.46, mod_openssl was integrated which introduced WOFF fonts error making previous API not to load and move to stalled condition. This issue has impact on chrome browser. Where as firefox does not had impact of this issue."

Can you please help us to fix it for smooth browsering on chrome browser?


Files

Chrome_browser.png (30 KB) Chrome_browser.png mohan1044, 2021-07-02 05:49
Actions #1

Updated by gstrauss almost 3 years ago

  • Status changed from New to Invalid
  • Priority changed from Normal to Low
  • Target version deleted (1.4.x)

Please read: How to get support

Start by testing with the latest lighttpd release.
lighttpd 1.4.59 was released Feb 2021.
lighttpd 1.4.54 was released May 2019. lighttpd 1.4.54 is out-of-date. If that is what is provided by your distro of choice, then your distro of choice is out-of-date.

Ask questions in the Forums (see tab near top of page)

We could see from release notes that "In lighttpd version 1.4.46, mod_openssl was integrated which introduced WOFF fonts error making previous API not to load and move to stalled condition. This issue has impact on chrome browser. Where as firefox does not had impact of this issue."

lighttpd 1.4 has always integrated with openssl. lighttpd 1.4.46 separated openssl support from the lighttpd core into a separate mod_openssl module.

Perhaps the versions of openssl and lighttpd have changed, along with your kernel and system libraries.

This issue has impact on chrome browser. Where as firefox does not had impact of this issue.

This does not sound like an issue with lighttpd.

Actions

Also available in: Atom