The implementation of HTTP header Logic

recently reading "schematic HTTP", there is no problem with the understanding of the protocol, but there is some confusion in the logical implementation.

who completes the segmentation and splicing of HTTP messages when transmitting in blocks? The segmentation is carried out in Server, so is the Web gateway (such as Nginx and other servers) or the Web framework (Flask,Tornado, etc.) to complete the segmentation? The same stitching task is done by the browser or the front-end code?
HTTP, for example, the following request header field If-xxx , is its logical implementation written in the business code by the Web framework of the server or when the Web application is developed?

Web python http http-first

Mar.07,2021

depends on the architecture of your server. For example, if your predecessor is directly Nginx, then these processes may be done by Nginx (or you can put them in Nginx-Lua); if there is no Nginx in the previous level, Node.js will take over everything directly, then these may be handled by Node.js. HTTP here just tells you how to run a network communication specification, and the specific implementation depends on how the server is structured.

Previous: RN achieves the following effect, but there is a problem with the iphonex simulator

Next: Problems with the sumoselect plug-in