How to detect malicious zip bombs uploaded by users and prevent unzip from being detonated

I saw this article on Hackernews about the zip bomb news. ycombinator. comitem? Id4... I just thought, if a user uploads a zip file to the server and the server is dumb to understand the pressure, isn't it a crash? How should I check it before the user uploads the zip file... what is the http://news.ycombinator.com/item for this zip bomb article on Hackernews? Id = 4...
I just thought, if a user uploads a zip file to the server and the server is dumb to understand the pressure, wouldn't it crash?

After a user uploads a zip file, how should he detect it before decompression to prevent the recurrence of the tragedy?
It is best to use python and php as examples. I think the web language should have this risk.

Reply content:

What is the http://news.ycombinator.com/item for this zip bomb article on Hackernews? Id = 4...
I just thought, if a user uploads a zip file to the server and the server is dumb to understand the pressure, wouldn't it crash?

After a user uploads a zip file, how should he detect it before decompression to prevent the recurrence of the tragedy?
It is best to use python and php as examples. I think the web language should have this risk.

Generally, the WEB server does not automatically decompress the zip file, while the virus check component of the mail server automatically decompress various types of compressed files, such as amavisd-new, which is exactly the case in that article.