[Varnish] #1355: ESI processing should also work when first character is a BOM

Thu Oct 10 18:23:15 CEST 2013

#1355: ESI processing should also work when first character is a BOM
------------------------+--------------------
 Reporter:  JohnMoylan  |       Type:  defect
   Status:  new         |   Priority:  normal
Milestone:              |  Component:  build
  Version:  3.0.4       |   Severity:  normal
 Keywords:  ESI, BOM    |
------------------------+--------------------
 ESI's are not firing on BOM'd content. If Varnish detects a Byte order
 Mark it should probably have an option to check if the next character a <
 instead of not processing it for ESI. This is going to be an issue with
 for environments with some or all content coming from a Microsoft workflow
 where not all BOM's might be easy to strip.

 <U+FEFF><!doctype html>
 <!-- Conditional comment for mobile ie7 http://blogs.msdn.com/b/iemobile/
 -->
 <!-- Appcache Facts http://appcachefacts.info/ -->
 <!--[if IEMobile 7 ]>    <html class="no-js iem7"> <![endif]-->
 <!--[if (gt IEMobile 7)|!(IEMobile)]><!-->
 <html class="no-js">
 <head>
 <meta charset="iso-8859-15">


 34 ObjHeader    c Content-Type: text/html
    34 ESI_xmlerror c No ESI processing, first char not '<'
    34 Gzip         c U F E 4066 16542 80 80 32463
    34 Gzip         c G F E 16542 4079 80 32552 32562
    34 VCL_call     c deliver
    34 VCL_return   c deliver
    34 TxProtocol   c HTTP/1.1
    34 TxStatus     c 200
    34 TxResponse   c OK
    34 TxHeader     c Cache-Control: max-age=180

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1355>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator