Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
litespeed_wiki:cache:litemage:troubleshooting:how-to-fix-rewrite-rule-which-break-litemage-esi [2017/05/11 21:12]
Jackson Zhang
litespeed_wiki:cache:litemage:troubleshooting:how-to-fix-rewrite-rule-which-break-litemage-esi [2017/05/11 21:46]
Jackson Zhang
Line 1: Line 1:
 ====== How to fix "an error occurred while processing this directive"?​ ====== ====== How to fix "an error occurred while processing this directive"?​ ======
  
-After enabling LiteMage, the store shows "an error occurred while processing this directive"​. ​+After enabling LiteMage, the store shows "an error occurred while processing this directive"​. ​All esi blocks got this error message and none of the ESI request was sent to the magento backend. 
 {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​an-error-occurred-while-processing-this-directive.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​an-error-occurred-while-processing-this-directive.png?​800 |}}
 +
 +Turn on litemage debug log, we only see the main request coming in, but no any subsequent esi request.
  
 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 both 80 and 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.
Line 22: Line 27:
 then  then 
   mv error_log log2check   mv error_log log2check
-then turn off the debug log:+then turn off the debug log, run the same command again:
   kill -USR2 <PID>   kill -USR2 <PID>
  
  • Admin
  • Last modified: 2017/05/16 13:33
  • by Lisa Clarke