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.

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

Advice for ServiceWorker implementation #256

Closed
mnot opened this issue Oct 31, 2016 · 1 comment
Closed

Advice for ServiceWorker implementation #256

mnot opened this issue Oct 31, 2016 · 1 comment

Comments

@mnot
Copy link
Member

mnot commented Oct 31, 2016

Perhaps we should add an appendix to help people do this?

@sebdeckers
Copy link

FYI/FWIW I've just implemented this spec via a service worker.

It would be nice if the spec clarified and defined the following. (I deduced it from @kazuho 's server and serviceworker implementations.)

  • HTTP header is called cache-digest. This is a very handy alternative to the HTTP2 frame which service workers can't access currently.
  • Base64 encoding must not be padded with = trailing.
  • String equivalent of the COMPLETE (0x2) flag for the HTTP header is complete and appended as ... base64 ...; complete (note the semicolon and white space)

Additionally more examples would be welcome, to aid implementors in validating their support. In particular the etags concatenation is unclear to me from the referenced spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants