Implementing URL-Encoded POST Requests in Go: A Deep Dive into http.NewRequest Method

Problem Background and Common Error Analysis

In Go language development, a typical error when using the http.NewRequest method involves incorrectly placing URL-encoded POST data in URL query parameters. As shown in the original code:

u.RawQuery = data.Encode()
urlStr := fmt.Sprintf("%v", u)
r, _ := http.NewRequest("POST", urlStr, nil)

This approach results in servers returning 400 BAD REQUEST responses because application/x-www-form-urlencoded data should be transmitted through the request body, not URL query strings.

Correct Implementation Method

URL-encoded payload data must be provided through the body parameter of the http.NewRequest method, which requires a type implementing the io.Reader interface. Here's the complete corrected implementation:

package main

import (
    "fmt"
    "net/http"
    "net/url"
    "strings"
)

func main() {
    apiUrl := "https://api.com"
    resource := "/user/"
    data := url.Values{}
    data.Set("name", "foo")
    data.Set("surname", "bar")

    u, _ := url.ParseRequestURI(apiUrl)
    u.Path = resource
    urlStr := u.String()

    client := &http.Client{}
    r, _ := http.NewRequest(http.MethodPost, urlStr, strings.NewReader(data.Encode()))
    r.Header.Add("Authorization", "auth_token=\"XXXXXXX\"")
    r.Header.Add("Content-Type", "application/x-www-form-urlencoded")

    resp, _ := client.Do(r)
    fmt.Println(resp.Status)
}

Key Technical Points Analysis

Data Encoding and Transmission: The url.Values.Encode() method converts key-value pairs into URL-encoded format strings, which are then wrapped as io.Reader interface implementations using strings.NewReader, ensuring correct data transmission to the request body.

Request Header Configuration: The Content-Type: application/x-www-form-urlencoded header must be set to explicitly inform the server about the request body data format. Additionally, authentication headers like Authorization need proper configuration.

Error Handling Improvements: Production code should include comprehensive error handling logic, covering error checks for URL parsing, request creation, and HTTP client execution phases.

Comparison with JSON Format

Although the question mentions potentially using application/json format, both formats serve different application scenarios. URL-encoded format is more suitable for simple form data, while JSON format is appropriate for complex structured data. The choice depends on specific API requirements and data characteristics.

Best Practice Recommendations

In practical development, using the http.PostForm function is recommended for simple form submissions. However, for advanced scenarios requiring fine-grained control over request headers, http.NewRequest with proper body parameter configuration remains the optimal choice. Always follow target API documentation requirements to ensure complete alignment between data format and transmission methods.