Do Summaly cache and proxy OpenGraph metadata from other servers? To avoid being marked as DDOS IP source.

[tassoman]

As administrator, I want to minimise http requests to third party servers, coming from my server, so that I can minimise risk of being marked into firewall blocklist against DDOS.

By using a Summaly server, do I can fetch once OpenGraph metadata from others, then store in a cache, and finally serve as proxed data? Would be enough to avoid being flagged as DDOS IP source from others?

[AmaseCocoa]

Searching shows that misskey-dev/summaly does not appear to cache OGP (though whether it actually caches may depend on proxy settings): #27

but, pull-request adding Cache-Control to response is opened: #42

If you need cache immediately, you may need to use a alternative-implementation or create your own fork...

[tassoman]

Thank you for digging into the code and pointing exactly to the matter. Was really appreciated.

Nowadays, I'm running Summaly by using Misskey.io container. The result I got was a proxed resource

This means my misskey configuration is proxying resources. So I guess: "until the resource is saved into misskey cache, no requests are leaving to others".

I guess #42 can solve in part the situation. But I was expecting Summaly was compiling a cache itself, taken from the filesystem/ram/volume.

If one administrator chose for RAM, then Redis usage maybe more appropriate. In my situation I'd prefer filesystem cache (either binary), and, maybe, a cache size limit. So that total cache can't grow more than... 1GB or custom setting.

Another situation, maybe is putting misskey outgoing requests behind a caching proxy, for example Squid or Nginx. But this situation is more complicated to setup.