Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:litemage:troubleshooting:how-to-fix-rewrite-rule-which-break-litemage-esi [2017/05/11 21:07]
Jackson Zhang created
litespeed_wiki:cache:litemage:troubleshooting:how-to-fix-rewrite-rule-which-break-litemage-esi [2017/05/11 21:12]
Jackson Zhang
Line 6: Line 6:
 Try to locate if the store uses some page optimization plugin, which could be the source of the problem, as it change the html after LiteMage inject esi:include for hole punching. In the end, such optimization plugin can not be located. Try to locate if the store uses some page optimization plugin, which could be the source of the problem, as it change the html after LiteMage inject esi:include for hole punching. In the end, such optimization plugin can not be located.
  
-A common cause is that something rewrite the URLs for ESI:include directives which breaks litemage. Need to turn of rewrite log and server debug log for it. If https is used for the store, make sure you enabled the rewrite log on 443 virtual host.+A common cause is that something rewrite the URLs for ESI:include directives which breaks litemage. Need to turn of rewrite log and server debug log for it. If https is used for the store, make sure you enabled the rewrite log on both 80 and 443 virtual host.
  
 You will need to add the following to the virtual host and restart web server. You will need to add the following to the virtual host and restart web server.
-  
   RewriteLogLevel 9   RewriteLogLevel 9
-  ​ 
 Then enable LSWS debug log by the following command Then enable LSWS debug log by the following command
   ps -ef | grep litespeed   ps -ef | grep litespeed
  • Admin
  • Last modified: 2017/05/16 13:33
  • by Lisa Clarke