- Go Web Scraping Quick Start Guide
- Vincent Smith
- 251字
- 2021-07-02 13:58:17
Request body
Query parameters are typically only used on HTTP GET requests. For requests where you are sending data to the server, such as POST and PUT requests, you would send a request body that holds all of your extra information. Request bodies are placed after the HTTP headers in an HTTP request, with a one-line space between them. The following is a hypothetical POST request for logging into an imaginary website:
POST /login HTTP/1.1
Host: myprotectedsite.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 38
username=myuser&password=supersecretpw
In this request, we are sending our username and password to myprotectedsite.com/login. The headers for this request must describe the request body so the server is able to process it. In this case, we declare that the request body be in the x-www-form-urlencoded format, which is the same format used for the query parameters in the Query parameters section. We could use alternative formats, such as JSON or XML or even plain text, but only if it is supported by the server. The x-www-form-urlencoded format is the most widely supported and is generally a safe bet. The second parameter we define in the header is the length of the request body in bytes. This allows the server to efficiently prepare for processing the data, or rejecting the request completely if it is too large.
The Go standard library has good support for building HTTP requests quite simply—if you are familiar with the structure, at least. We will revisit how this is done later in this chapter.
- 社交網絡對齊
- GPS/GNSS原理與應用(第3版)
- Django 2 by Example
- Web Application Development with R Using Shiny
- 信息通信網絡建設安全管理概要2
- 計算機網絡工程實用教程(第2版)
- Spring 5.0 Projects
- Learning Storm
- 語音信號處理及Blackfin DSP實現
- Getting Started with Memcached
- 網絡空間全球治理觀察
- TCP/IP基礎(第2版)
- 現代通信系統(第5版)
- Getting Started with tmux
- Hands-On Reactive Programming in Spring 5