Other than HTTP cookies, there’s nothing in the protocol specification about forwarding headers. The client needs to implement this functionality.
More Related Contents:
- application/x-www-form-urlencoded or multipart/form-data?
- Do I need Content-Type: application/octet-stream for file download?
- Maximum on HTTP header values?
- Uses of content-disposition in an HTTP response header
- ‘Refresh’ HTTP header
- Is there a practical HTTP Header length limit?
- Detecting the character encoding of an HTTP POST request
- What are all the possible values for HTTP “Content-Type” header?
- Ideal HTTP cache control headers for different types of resources
- Remove http referer
- HTTP Range header
- How can I get the clients IP address from HTTP headers?
- Content-Length header with HEAD requests?
- Difference between Content-Range and Range headers?
- How does “304 Not Modified” work exactly?
- What is q=0.5 in Accept* HTTP headers?
- How big can a user agent string get?
- What is Cache-Control: private?
- How can I find out whether a server supports the Range header?
- What is a full specification of X-Forwarded-Proto HTTP header?
- What HTTP response headers are required
- Does the HTTP Protocol support multiple content types in response headers?
- What is the http-header “X-XSS-Protection”?
- What is HTTP “Host” header?
- What does HTTP/1.1 302 mean exactly?
- HTTP Cache Control max-age, must-revalidate
- Is the Content-Length header required for a HTTP/1.0 response?
- Is REST DELETE really idempotent?
- Keep-alive header clarification
- S3: How to do a partial read / seek without downloading the complete file?