Skip to content
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

LiteSpeed broken layout incompatibility #2776

Closed
4 tasks
piotrbak opened this issue Jun 15, 2020 · 18 comments · Fixed by #3713
Closed
4 tasks

LiteSpeed broken layout incompatibility #2776

piotrbak opened this issue Jun 15, 2020 · 18 comments · Fixed by #3713
Assignees
Labels
3rd party compatibility Issues related to 3rd party compatibility like theme, plugin or hosting effort: [XS] < 1 day of estimated development time priority: high Issues which should be resolved as quickly as possible severity: major Feature is not working as expected and no work around available
Milestone

Comments

@piotrbak
Copy link
Contributor

piotrbak commented Jun 15, 2020

Describe the bug
When using LiteSpeed (and seems that in connection with WooCommerce), double click on the WooCommerce page creates a broken layout cache.

I wasn't able to replicate this on pages other than WooCommerce ones.

To Reproduce
Steps to reproduce the behavior:

  1. On WooCommerce site hosted on LiteSpeed
  2. Clear all caches, including OPCache
  3. Go to the taxonomy page
  4. Double-click on the chosen product
  5. See if the layout is broken

Expected behavior
WP Rocket caching the pages correctly.

Screenshots
Double click on the product page:
https://jmp.sh/ve9YdcY

Double click on taxonomy page:
https://jmp.sh/4n8e1nJ

Additional context
I was working on one ticket related to this issue, I was pretty sure that it's related to the HTTP/3 protocol and QUIC, but I have a second ticket with HTTP/2.

Nothing special in the WP Debug log. The cached HTML file just stops at some point.

In the first ticket, it was happening only for mobiles (still not for all), in the second one, I've reproduced it on the desktop.

I'm getting more information regarding the second environment, as it seems that it has a shared cache directory.

Related tickets:

  1. We have access to the full cPanel and we can test there whatever needed:
    https://secure.helpscout.net/conversation/1173326494/167375?folderId=2415573

  2. New ticket (from screencast), still getting more information about the environment:
    https://secure.helpscout.net/conversation/1165493465/165403?folderId=2415573

Backlog Grooming (for WP Media dev team use only)

  • Reproduce the problem
  • Identify the root cause
  • Scope a solution
  • Estimate the effort
@piotrbak piotrbak changed the title LiteSpeed broken layout incompatibility [WIP] LiteSpeed broken layout incompatibility Jun 15, 2020
@BenHarris
Copy link

We hit this today too. Have temporarily rolled back to 3.5.5.1

@piotrbak
Copy link
Contributor Author

@BenHarris This issue is not related to this one:
#2767

Please check if the 3.6.0.3 version fixes your problem. If not, contact us via support and mention this GitHub issue.

@vmanthos
Copy link
Contributor

There is a related ticket here: https://secure.helpscout.net/conversation/1213394116/177393
Check my notes: https://secure.helpscout.net/conversation/1213394116/177393/#thread-3526587635

This is WIP, but I'll be on leave, so I'm adding here my findings so far.

As Piotr found, the issue can occur when there are multiple clicks on the link of a product. I found this can happen with normal pages too. This site is hosted on a LiteSpeed server, as in previous cases.

When doing multiple clicked, some of the requests are canceled:

Full-Scale image > https://i.vgy.me/TWjbn5.jpg

The caching process stopped in these two checks:

One obviously passes through resulting into only a part of the page being cached, e.g. http://snippi.com/s/pvej1ql

@vmanthos
Copy link
Contributor

vmanthos commented Sep 7, 2020

@arunbasillal arunbasillal added 3rd party compatibility Issues related to 3rd party compatibility like theme, plugin or hosting status: work in progress Indicates and issue or PR is in work in progress labels Sep 7, 2020
@vmanthos
Copy link
Contributor

Potentially related ticket:
https://secure.helpscout.net/conversation/1285231945/195643/

This is again a WooCommerce site on a Litespeed server.

@vmanthos
Copy link
Contributor

@arunbasillal
Copy link
Contributor

@piotrbak Is this issue still WIP? If not, can you please update the title?

@arunbasillal arunbasillal added the priority: high Issues which should be resolved as quickly as possible label Jan 21, 2021
@vmanthos
Copy link
Contributor

vmanthos commented Feb 9, 2021

Potentially related ticket: https://secure.helpscout.net/conversation/1419934340/237835/

The site is hosted on a LiteSpeed server, and pages are randomly cached incomplete, e.g.: http://snippi.com/s/0rj03ck

@NataliaDrause
Copy link
Contributor

@piotrbak piotrbak changed the title [WIP] LiteSpeed broken layout incompatibility LiteSpeed broken layout incompatibility Feb 15, 2021
@piotrbak piotrbak added severity: major Feature is not working as expected and no work around available and removed status: work in progress Indicates and issue or PR is in work in progress labels Feb 15, 2021
@vmanthos
Copy link
Contributor

@camilamadronero-zz
Copy link

@vmanthos
Copy link
Contributor

@AscensionAynat
Copy link

AscensionAynat commented Mar 27, 2021

Hi, is there already a solution for this issue? I'm having this problem.

@sandyfigueroa
Copy link
Contributor

sandyfigueroa commented Mar 30, 2021

Related ticket: https://secure.helpscout.net/conversation/1460570318/249648/

The client applied the changes that Vasilis proposed and says that fixes the issue.

@NataliaDrause
Copy link
Contributor

@vmanthos
Copy link
Contributor

vmanthos commented Apr 5, 2021

@NataliaDrause
Copy link
Contributor

@Tabrisrp Tabrisrp added effort: [XS] < 1 day of estimated development time and removed needs: grooming labels Apr 7, 2021
@Tabrisrp Tabrisrp added this to the 3.9 milestone Apr 7, 2021
@NataliaDrause
Copy link
Contributor

Tabrisrp added a commit that referenced this issue Apr 14, 2021
…ing cache (PR #3713)

* Process buffer only if there is a closing </html>
* Do not look for </html> when it's a REST API request
* formatting update
* update pattern for unexpected spacing

Co-authored-by: Rémy Perona <remperona@gmail.com>
@Tabrisrp Tabrisrp mentioned this issue Apr 14, 2021
13 tasks
@Tabrisrp Tabrisrp mentioned this issue May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party compatibility Issues related to 3rd party compatibility like theme, plugin or hosting effort: [XS] < 1 day of estimated development time priority: high Issues which should be resolved as quickly as possible severity: major Feature is not working as expected and no work around available
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants