You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the main advantages is that it will also enable HTTP/2 server push of critical Gatsby assets through the Link headers. By default, the plugin will add HTTP/2 assets to server push the critical Gatsby scripts (ones that have the preload attribute already) and also adds some basic security and caching headers.
Integrated gatsby-plugin-netlify like documented in the "Hosting &
Continuous Deployment"”" design concept. It allows to automatically
generate a `_headers` file and a `_redirects` file at the root of the
public folder to configure HTTP headers (3) and redirects (4) on
Netlify.
One of the main advantages is that it also enables HTTP/2 server push of
critical Gatsby assets through the `Link` headers. By default, the
plugin adds HTTP/2 assets to server push the critical Gatsby scripts
(ones that have the `preload` attribute already) and also adds some
basic security and caching headers.
References:
(1) https://www.npmjs.com/package/gatsby-plugin-netlify
(2) #46
(3) https://www.netlify.com/docs/headers-and-basic-auth
(4) https://www.netlify.com/docs/redirects
Associated epic: GH-46GH-89
This issue documents the integration of gatsby-plugin-netlify like documented in the “Hosting & Continuous Deployment” design concept. It allows to automatically generate a
_headers
file and a_redirects
file at the root of the public folder to configure HTTP headers and redirects on Netlify.One of the main advantages is that it will also enable HTTP/2 server push of critical Gatsby assets through the
Link
headers. By default, the plugin will add HTTP/2 assets to server push the critical Gatsby scripts (ones that have thepreload
attribute already) and also adds some basic security and caching headers.Tasks
The text was updated successfully, but these errors were encountered: