I already see content-encoding: gzip on the initial response from my setup (2.6MB and 636KB transferred). It could be the nginx reverse proxy doing that, but gzip_proxied defaults to off so I think that's coming from tiddlywiki's listener. I don't see it on subsequent responses.
There's probably more improvement to be had from adding headers for controlling cache behavior. (ETag) I found a project providing an nginx module for etags on dynamic content <https://github.com/dvershinin/ngx_dynamic_etag>, but I haven't tried it yet. On Sunday, September 15, 2019 at 6:35:12 AM UTC-4, Mohammad wrote: > > Aren has given a great proposal at > > https://github.com/Jermolene/TiddlyWiki5/issues/4262#issue-493686392 > > to gzip the $:/core and minimize the size of core! > > I support his idea! If you agree discuss this or vote on GitHub > > --Mohammad > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b20f9179-49de-40aa-bbf5-0190871cfe4e%40googlegroups.com.
