On Wednesday, December 3, 2014 2:17:38 PM UTC+1, Tobias Beer wrote: > > Hi Jeremy, > > >> As Mario points out, visiting the direct URL of the SVG image doesn't >> work because the server content type is set incorrectly. >> > > 2 Questions: > > 1) Did that change in the core or was it always the case that the browser > would not render such svg's correctly? >
As you found out: http://bbz-dormagen-tools.de/TW/01-test/images/MotovunJack.svg contains the svg. But as you can see, the browser can't handle it correctly, since the server doesn't set the content-type in the header. All web servers have a configuration, that tells them how the default content-type should look like. mainly based on the extension. If we know the server eg: apache, nginx ... we would be able to find the setting, that needs to be changed.... But in normal cases, the IT guy, that did set up the server will know it already :) > 2) Would an alternative to using *_canonical_uri* be to change something > in the server configuration? > Not really. Embedding the svg and transcluding it would be a possibility, but doesn't solve the general server setting problem. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
