Closed yomed closed 9 years ago
@yomed the best thing to do is probably build this XML file with Lasso and Marko. Is that reasonable for you?
Yeah, I think so. I ended up handling all the favicon resources outside of lasso because I think it simplifies things here, but this is more of a special case.
From the docs, you can lasso generic resources and get the dynamic urls:
But some browsers look for static files (json/xml) which hold references to those favicon urls. For example, IE11 looks for this:
Is there a way in lasso to handle these references to point to the correct resources?