what is the first header a browser transmits in an HTTP 1.1 GET request
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
if you want to trace sent and recieved headers, i'd recommend using a very useful application called httpwatch. from their site you shall learn many useful things
http://www.httpwatch.com/h
here is a typical get header sent to their site, and as you see, get is the very first thing posted
Business Accounts
Answer for Membership
by: RurnePosted on 2008-01-24 at 10:35:28ID: 20735853
"From the HTTP/1.1 specification (http://www.w3.org/Protoco
Request = Request-Line ; Section 5.1
*(( general-header ; Section 4.5
| request-header ; Section 5.3
| entity-header ) CRLF) ; Section 7.1
CRLF
[ message-body ] ; Section 4.3
5.1 Request-Line
The Request-Line begins with a method token, followed by the Request-URI and the protocol version, and ending with CRLF. The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
Request-Line = Method SP Request-URI SP HTTP-Version CRLF"
So, the first line in any request is always going to be the GET action itself. After that, it's an unordered list of headers, though typically it's a Host: command to specify which virtual host you're trying to contact. I have seen user agents issue an Accept: before the Host: command and still work, though, so it just depends. However, Host: is the only required header for a valid HTTP/1.1 connection, so it typically gets priority.