This page is about Caddy 1 and will stay here forever.

User Guide


push enables and configures HTTP/2 server push.

Server push can accelerate page loads by sending resources that the server knows the client will need, but has not yet asked for. It is not a replacement for WebSockets. It must also be configured carefully, especially with regards for client-side caching, or pushing can actually decrease performance. If a client caches a resource after the first time it is pushed, subsequent pushes of the same resource are unnecessary.

Caddy knows which resources to push either from rules you provide in the Caddyfile or from Link headers coming from some upstream.



Enables server push for any request by reading the Link HTTP header of the response. Useful if you're proxying to a backend app with proxy or fastcgi, for example, that sets the Link headers for preload purposes.

To configure a basic push rule:

push path [resources...]

To push many resources that won't fit on a single line or to change the method or headers of the synthetic request used to initiate the pushes, open a block:

push path [resources...] { method method header name value resources }


Enable server push for all requests using Link headers:


Push Google Analytics script for all requests (not cache-aware):

push / /ga.js

Push a couple CSS files for requests to the home page:

push /index.html /common.css /home.css

Push many resources to the home page:

push /index.html { /resources/css/common.css /resources/css/home.css /resources/css/compiled.css /resources/js/main.js /resources/js/jquery.min.js /resources/images/logo.png /resources/images/background.jpg }

Specify a method and header for all push requests:

push { method HEAD header MyHeader "The value" }

Need help with this feature?

Join us in the Caddy forum, where the open source community gathers to share their knowledge.

Does your company use Caddy?

Purchase a commercial license to use Caddy with your business and for basic email support, along with other benefits!