I still can't reproduce #487 locally, but I think the issue could be caused by a redirect that Chrome has some kind of undocumented defenses against (insecure address surely isn't the issue). We're just going to try this address it redirects to
Please excuse me merging this without review: we're just changing a link to another valid link
I still can't reproduce #487 locally, but I think the issue could be caused by a redirect that Chrome has some kind of undocumented defenses against (insecure address surely isn't the issue). We're just going to try this address it redirects to
Please excuse me merging this without review: we're just changing a link to another valid link