Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify subresource steps. #4

Merged
merged 1 commit into from Jul 29, 2021
Merged

Clarify subresource steps. #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Expand Up @@ -62,11 +62,15 @@ out of signing, set the `Cache-Control` header to include `private` or

LCP can be further improved by instructing Google Search to prefetch
render-critical subresources for the page. To do so, add a `Link: rel=preload`
header and a matching `Link: rel=allowed-alt-sxg` header, as in [this
header and a matching `Link: rel=allowed-alt-sxg` header in the upstream server
(the `html_host`), as in [this
example](https://github.com/WICG/webpackage/blob/main/explainers/signed-exchange-subresource-substitution.md#:~:text=a%20preload%20header%20and%20an%20allowed-alt-sxg%20header).
To compute the `header-integrity` for each subresource, run:

``` bash
$ go install github.com/WICG/webpackage/go/signedexchange/cmd/dump-signedexchange@latest
$ dump-signedexchange -uri $URL -headerIntegrity
```

To ensure the `header-integrity` remains stable, eliminate frequently changing
headers from the upstream response such as `Date`.