I'm told that we're not blocking beacon requests from secure sites to non-secure endpoints if the endpoint results from a redirect. That is:

* https://example.com/ sends a beacon request to https://redirector.com/
* https://redirector.com/ responds with a 302 to http://non-secure.com/

In this case, the initial request would be allowed, and the redirect ought to be blocked.