I would like to create a chain of HTTPS 302 redirects to a series of domains (for research purposes). I want also to make sure that I can do a redirect if one of the certificates in my chain has been rejected. That is I would like the following steps to occur:
- Do a redirect to URL 1
- The certificate gets rejected on the client due to some reason.
- Certificate rejection sends some sort of an indicator on the server, which then subsequently sends a redirect to another URL 2 with a valid certificate.
I do understand that a successful TLS negotiation needs to occur, before I am able to send an HTTPS 302 redirect to another location, but I was wondering if there is any indication on the server when an
HTTPS certificate has been rejected (apart from not receiving any request even after some delay), to enable it to send a redirect to another URL with a valid certificate.