Analysis and Solution of Content-Type Header Space Issue in cURL Commands

Problem Phenomenon and Background

When using the cURL tool to send HTTP requests, developers often encounter the error message curl: (6) Could not resolve host: application. This error is typically accompanied by an HTTP 415 Unsupported Media Type response, indicating that the server cannot properly process the request's content type.

From the provided case, the user executed the following command:

curl -i -H 'Content-Type: application/json' -d '{"Code":"FR","Name":"France"}' http://127.0.0.1:8080/countries

The server returned complete error information:

curl: (6) Could not resolve host: application
HTTP/1.1 415 Unsupported Media Type
Content-Type: application/json; charset=utf-8
X-Powered-By: go-json-rest
Date: Sat, 02 Apr 2016 05:31:20 GMT
Content-Length: 73

{
"Error": "Bad Content-Type or charset, expected 'application/json'"
}

Root Cause Analysis

After in-depth analysis, the core of the problem lies in cURL's command-line parameter parsing mechanism. When a space is added after the colon in the -H header parameter, cURL mistakenly parses the content after the space as a new parameter or hostname.

Specifically, the incorrect command format:

curl -H Content-Type: application/json

The cURL parser identifies Content-Type: as a complete header field, while mistaking application/json for another parameter or hostname. Since application is not a valid hostname, cURL fails when attempting to resolve it, resulting in the Could not resolve host: application error.

The correct command format should be:

curl -H Content-Type:application/json

This format ensures that the entire Content-Type:application/json is passed to cURL as a complete header parameter.

Technical Details Deep Dive

As a command-line tool, cURL's parameter parsing follows specific rules:

• Spaces serve as parameter separators
• Quotes are used to contain parameter values that include spaces
• Colons act as key-value separators in header parameters

At the HTTP protocol level, the Content-Type header specifies the media type of the request body. When the server expects application/json but receives an incorrect header, it returns a 415 status code.

The case in the reference article further confirms this issue. Users encountered similar parsing errors when using the Confluence REST API, ultimately resolving the problem by correcting the header format.

Solutions and Verification

Multiple solutions are provided for this issue:

Solution 1: Remove space after colon

curl -H Content-Type:application/json -d '{"Code":"FR","Name":"France"}' http://127.0.0.1:8080/countries

Solution 2: Use quotes to wrap complete header

curl -H "Content-Type: application/json" -d '{"Code":"FR","Name":"France"}' http://127.0.0.1:8080/countries

In Windows environments, due to differences in command-line parsing, additional escaping may be required:

curl -H "Content-Type: application/json" -d "{\"Code\":\"FR\",\"Name\":\"France\"}" http://127.0.0.1:8080/countries

Verification methods include using the --verbose parameter to view detailed request processes:

curl --verbose -H Content-Type:application/json http://127.0.0.1:8080/countries

This displays the complete HTTP request and response process, aiding in problem diagnosis.

Best Practice Recommendations

Based on deep understanding of cURL and HTTP protocols, the following best practices are recommended:

• Always use quotes to wrap header parameters containing special characters
• Pay attention to command-line parsing differences when migrating between Windows and Unix-like systems
• Use the --verbose parameter for debugging
• Verify the server's Content-Type expectations
• Consider using tools like Postman for API testing and command generation

As mentioned in the reference article, users ultimately solved the problem using correct cURL commands generated by Postman, highlighting the importance of using professional tools to assist development.

Conclusion

The space issue in cURL's Content-Type header is a common but easily overlooked technical detail. By deeply understanding command-line parameter parsing mechanisms and HTTP protocol specifications, developers can avoid such errors and improve development efficiency. The analysis and solutions provided in this article are applicable to various scenarios using cURL for HTTP communication.