diff options
| author | rinpatch <rinpatch@sdf.org> | 2020-03-11 17:58:25 +0300 |
|---|---|---|
| committer | rinpatch <rinpatch@sdf.org> | 2020-03-11 17:58:25 +0300 |
| commit | c3b9fbd3a759d281ef2e81395b78549e43cab63c (patch) | |
| tree | ab8351c4c7d2b6f930f49d9c230749dec2ab4201 /test/plugs/cache_control_test.exs | |
| parent | 9dbf493b65826d3421f568eb18651deeba8276e2 (diff) | |
| download | pleroma-c3b9fbd3a759d281ef2e81395b78549e43cab63c.tar.gz | |
Revert "Set better Cache-Control header for static content"
On furher investigation it seems like all that did was cause unintuitive
behavior. The emoji request flood that was the reason for introducing it
isn't really that big of a deal either, since Plug.Static only needs to
read file modification time and size to determine the ETag.
Closes #1613
Diffstat (limited to 'test/plugs/cache_control_test.exs')
| -rw-r--r-- | test/plugs/cache_control_test.exs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/plugs/cache_control_test.exs b/test/plugs/cache_control_test.exs index 005912ffb..6b567e81d 100644 --- a/test/plugs/cache_control_test.exs +++ b/test/plugs/cache_control_test.exs @@ -9,7 +9,7 @@ defmodule Pleroma.Web.CacheControlTest do test "Verify Cache-Control header on static assets", %{conn: conn} do conn = get(conn, "/index.html") - assert Conn.get_resp_header(conn, "cache-control") == ["public max-age=86400 must-revalidate"] + assert Conn.get_resp_header(conn, "cache-control") == ["public, no-cache"] end test "Verify Cache-Control header on the API", %{conn: conn} do |