From 4246e138f9512686413e97878659ef953337e57b Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Sun, 19 May 2019 16:14:09 -0700 Subject: [PATCH] Typo fix --- docs/performance.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/performance.rst b/docs/performance.rst index d564de60..976cf19c 100644 --- a/docs/performance.rst +++ b/docs/performance.rst @@ -67,7 +67,7 @@ You can enable these hashed URLs in two ways: using the :ref:`config_hash_urls` With hashed URLs enabled, any request to e.g. ``/mydatabase/mytable`` will 302 redirect to ``mydatabase-455fe3a/mytable``. The URL containing the hash will be served with a very long cache expire header - configured using :ref:`config_default_cache_ttl_hashed` which defaults to 365 days. -Since these responses are cached for a long time, you may wish to build API clients against the non-hashed version of these URLs. These 302 redirects are served extremely quickly, so this should still be a performant way to work agaist the Datasette API. +Since these responses are cached for a long time, you may wish to build API clients against the non-hashed version of these URLs. These 302 redirects are served extremely quickly, so this should still be a performant way to work against the Datasette API. If you run Datasette behind an `HTTP/2 server push `__ aware proxy such as Cloudflare Datasette will serve the 302 redirects in such a way that the redirected page will be efficiently "pushed" to the browser as part of the response, without the browser needing to make a second HTTP request to fetch the redirected resource.