Скачать с ютуб video #3 | First Flask Application and HTTP messages (Request and Response) in Bad Pronunciation в хорошем качестве

video #3 | First Flask Application and HTTP messages (Request and Response) in Bad Pronunciation

Dear friends, in this video I created the trivial "Hello, World!" #Flask app, and tried to explain the Flask developmental #Server and the basic mechanism by which the Client communicates through #HTTP message with the Server. This video also tries to explain the basic anatomy of HTTP messages, their types and various status codes in the response type HTTP messages. Below are some more points about HTTP message: ➡️ The server tries to find the desired object and, if successful, sends the object to the client in an HTTP response, along with the type of the object, the length of the object, and other information. ➡️ In HTTP, #idempotent methods are those that can be called multiple times without different outcomes. That means, whether you make the request once or many times, the result on the server is the same (excluding things like logs or rate limiting). GET, DELETE, PUT are the example of this kind. ➡️ HTTP carefully tags each object being transported through the Web with a data format label called a #MIME type. Web servers attach a MIME type to all HTTP object data. When a web browser gets an object back from a server, it looks at the associated MIME type to see if it knows how to handle the object. ➡️ HTTP is stateless, that means each HTTP request is independent and carries all the information the server needs to fulfill it. The server does not remember anything about previous requests. It doesn't retain client state between different requests unless you explicitly implement mechanisms for that (like sessions or tokens for login etc).