I did a few searches on this topic, and, to my surprise, it seems that people have already done this. I found a description here , but it does not provide a public test URI, so I could not verify the behavior of the browser on this. It also mentions the decision to send the archive file to the client. But I guess that is not what you are looking for, right?
Here 's another article showing an example with multiple answers. Unfortunately, the demo URI does not seem to work anymore.
So the situation is this: HTTP response responses can be executed. There are client (several) libraries for processing them in the application code. It is necessary to check the behavior of the browser ( here is the voice ). Using this feature seems experimental and can only be recommended. You can control both ends of the connection to fix compatibility issues.
source share