I wish HTTPS origins were allowed to define a set of certificates to trust. Imagine a game architecture where each game server has its own self-signed certifica

I wish HTTPS origins were allowed to define a set of certificates to trust. Imagine a game architecture where each game server has its own self-signed certificate. For example, imagine you download a game client via HTTPS, and the game client downloads a list of official servers from the same origin. I want the HTTPS origin to be able to say "for this webpage load, trust these certificates, because they originated from an HTTPS origin." Instead of making HTTPS hierarchical through a certificate chain, this let's it be dynamic (script-controlled) and sideways. Thoughts?