How is a POST request?

Hello, tell me, when we fill the form and send something to the database.
What is the formation of a post request?
Rather, it is created in the likeness of a get request, the same in the address line of a long string of addresses, commands and the fact that we ship and after it all goes to the server?
June 14th 19 at 20:57
2 answers
June 14th 19 at 20:59
Solution
POST is passed in the request body.

https://webgyry.info/http-zapros-metodom-post/
Another difference from GET to POST method, the POST method hides all it passes the variables and values that you have in your body (Entity-Body). In the case of the GET method they were stored in the request line (Request-URI).
- rhianna_Fee commented on June 14th 19 at 21:02
I understand that is the text of 35 characters?
And will look like the query if we submit the Text(title of video) and video or picture?
It will be 2 post request or one?( in terms of how it will look in Content-type)
And as it looks more complete if we send the data in a database called BD in the Video section?
There has been said, it is more difficult to intercept.
What does it mean to intercept, or rather, how, as it was written above that all the data hidden?
POST / HTTP/1.0\r\n
Host: www.site.ru\r\n
Referer: <a href="http://www.site.ru/index.html\r\n">http://www.site.ru/index.html\r\n</a>
Cookie: income=1\r\n
Content-Type: application/x-www-form-urlencoded\r\n
Content-Length: 35\r\n
\r\n
login=Dima&password=12345
- Ewell commented on June 14th 19 at 21:05
June 14th 19 at 21:01
Solution
When the GET request, parameters are passed in the link.
When a POST request, parameters are passed in the body of this request, along with data if any (files for example). The link is not changing. Although it can contain for additional processing, but this is how the server part is written.
Where and how is the body?
As I understand, a body is generated on the server when we make him a Get request?
If in Get we can see it clearly and can even record in the address bar, how then is the case with the Post? - rhianna_Fee commented on June 14th 19 at 21:04
Where and how is the body?

In a web browser or other http client.
Well as:
POST link HTTP/1.1
<headers>
Content-Type: application/x-www-form-urlencoded
Content-length: size of request body in bytes
<blank line>
When x-www-form-urlencoded actually part of the link (as in GET) is the request body:
param1=123123¶m2=345345¶m3=45676567

when multipart/form-data is more difficult, they are used when there is a form with a submit button usually:
POST link HTTP/1.1
<headers>
Content-Type: multipart/form-data; boundary=<the separator, for example: Asrf456BGe4h>
Content-length: size of request body in bytes
<blank line>
--Asrf456BGe4h
Content-Disposition: form-data; name="<the name of the field>"
<blank line>
<the value of the field>
--Asrf456BGe4h
...more fields
Asrf456BGe4h ---- <- the end of the form data.
<blank line> - Ewell commented on June 14th 19 at 21:07
i.e. the Submit button and everything in the form tag in no way relate to the address bar, and only communicate with the Browser and the browser already sends everything to the server?
What about mail then, because we can mail from the command line to send?
Isn't this the same post request? - Ewell commented on June 14th 19 at 21:10
What about mail then, because we can mail from the command line to send?

And how do You know that the application which You are using the command line run does not make a post request to transfer data? - abigail36 commented on June 14th 19 at 21:13
all depends on how the server is written. - Ewell commented on June 14th 19 at 21:16
and do not tell me a tutorial or an article, know where about it in detail?
I how many searched, everywhere brief description of how to create a standard server.
And so that was described by the conventions of technique, impact, in more depth, as you said, it all depends on how it is written the server., I have not found or maybe not somewhere realized. - abigail36 commented on June 14th 19 at 21:19
Wikipedia generally normally describes HTTP.
In General, HTTP is just a transport for a certain set of data here and there. And already how to use it, is decided by the developer. For example, a web-site where there is a client side in the role of the browser and the server. - abigail36 commented on June 14th 19 at 21:22

Find more questions by tags Web Development