3 ms·
That sounds like the event was forcing the use of an HTTP proxy server with over-eager caching. But in 2016, that would be a bit anachronistic..
by vanviegen 6y ago
That sounds like the event was forcing the use of an HTTP proxy server with over-eager caching. But in 2016, that would be a bit anachronistic..