Incompatibility between Solid's markers and nginx Server Side Includes (SSI) about dom-expressions HOT 5 CLOSED

I made some digging and it appears that quite a few web servers are using these kind of markers:

• Apache SSI <!--# ...
• Nginx SSI <!--# ...
• Cherokee uses SSI <!--# ...
• Tomcat uses SSI <!--# ...
• Lighttpd uses SSI <!--# ...
• IIS uses SSI <!--# ...
• Varnish which uses ESI <!--esi ... & <esi:include ...
• Caddy Server uses templates for SSI {{include ...}}
• Cloudflare ESI <esi:include ...

from dom-expressions.

Ok good to know. We can look at changing this but it applies to both the compiler and the runtime output which means I need to do this as a minor change minimum so that we can line them up.

from dom-expressions.

I mean they are HTML comments. Which I'm gathering we all need to use. Is specifically the # that is problematic for them?

from dom-expressions.

Yes, for example for nginx here's the syntax:

 SSI commands have the following generic format:

<!--# command parameter1=value1 parameter2=value2 ... -->

So yeah the # is part of the syntax for them, and after their transformation, this comment has disappeared altogether. Then hydration fails.

from dom-expressions.

The sequence beginning <!--#token is the convention for a server-side include.
e.g. https://www.w3.org/Jigsaw/Doc/User/SSI.html

lighttpd mod_ssi (when enabled) will detect <!--#--> as an invalid server-side include (SSI) empty token and will pass the comment string through unmolested, but other servers configured to process the response for server-side includes might replace that character sequence with an error string.

from dom-expressions.