> Hi there uwsgi friends! > > One of our users is keen on svg images, and I've been struggling to get > them served correctly. > > In some cases we serve them directly from our own code, and then they > work ok if I set > > Content-Type: image/svg+xml > Content-Encoding: gzip > > But sometimes they are served using the uwsgi static files tool > (static-map). And in that case, uwsgi recognises the mimetype > correctly, but it doesn't set the content-encoding, and that confuses > the web browser. > > Now, admittedly, I would call this a bug in the web browser, but we > can't control that easily, so is there a way to tell uwsgi's static > files handler to add a special content-encoding header to .svgz files? > > Or have I misunderstood something? > >
route = \.svgz$ addheader:Content-Encoding: gzip But, honestly i find it quite strange (it like telling the browser that a tar.gz file as the gzip encoding...) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
