handle changed -webkit-fill-available semantics

Chromium changed how this works to better match the evolving
specification and our usage effectively became a no-op.

1 files changed, 3 insertions, 3 deletions

diff --git a/nginx/nginx.conf b/nginx/nginx.conf
index 517aa971..36b311a4 100644
--- a/nginx/nginx.conf
+++ b/nginx/nginx.conf
@@ -151,12 +151,12 @@ http {
 
         location = /404 {
             internal;
-            http2_push /grapheneos.css?23;
+            http2_push /grapheneos.css?24;
         }
 
         location = /404.html {
             internal;
-            http2_push /grapheneos.css?23;
+            http2_push /grapheneos.css?24;
         }
 
         location ~ "^(.*)/index$" {
@@ -197,7 +197,7 @@ http {
             include /etc/nginx/snippets/security-headers.conf;
             add_header Cache-Control "public, max-age=1800";
             try_files $uri $uri.html $uri/ =404;
-            http2_push /grapheneos.css?23;
+            http2_push /grapheneos.css?24;
         }
     }