Hello again. I continue with my experiments on serving Wallabag via tipidee. Profiling the requests I find one JS file takes about 20% of the time, and the single longest individual download (other requests take long due to PHP), so I tried compressing it and serving it compressed, redirecting via symlink. However, there doesn't seem to be a direct way to tell tipidee to inform the browser what the encoding is. I guess one option is to use a little CGI script to add the header, but maybe it can be handled by tipidee like content-type is.
So, questions: 1. Does the CGI idea make sense for right now? Or is there an obvious flaw I'm missing? 2. Does the feature sound reasonable for a future version of tipidee? Cheers! Mario.
