Nick Harper

Feel free to send a pull request with that change.

(See also issue #75)

That sounds incredibly useful, even if it's only partially complete.

I did some experimenting with increasing the timeout on my workstation and here are the results: 15 second timeout: First call to /api/v2/update succeeds in loading all 51,718 HSTS entries...

I added some logging to PutStates and statesForQuery (the latter included a trial code change to use `Client.Run` and `Next` instead of `Client.GetAll`) to measure how many entries can be...

That was testing with the local emulator. I’m thinking of next testing deploying to a test appengine instance and datastore. It should be easy enough to create a new project...

Today, I had 5 unsuccessful attempts (4 500 errors, 1 502 nginx error) loading /api/v2/update before it succeeded. The successful run took 38.4s.

@lgarron do you remember why 3 was used as maxRedirects in [redirects.go](https://github.com/chromium/hstspreload/blob/be995c98f169479ab1938d94ecad0d95b42ea31a/redirects.go)?

Once case where the redirect limit of 3 is causing an issue is with a domain that redirects to an identity provider, and that IdP takes more than 2 redirects...

> If someone has a legitimate need to redirect from https://hstspreloadcandidate.com to http://www.somethingelse.com why should this project deny hstspreloadcandidate.com to be added to the hsts preload list? The benefit of...