• Complain

Wong - HTTP Pocket Reference

Here you can read online Wong - HTTP Pocket Reference full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Sebastopol;CA, year: 2000;2009, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

No cover
  • Book:
    HTTP Pocket Reference
  • Author:
  • Publisher:
    OReilly Media
  • Genre:
  • Year:
    2000;2009
  • City:
    Sebastopol;CA
  • Rating:
    5 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 100
    • 1
    • 2
    • 3
    • 4
    • 5

HTTP Pocket Reference: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "HTTP Pocket Reference" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Table of Contents; HTTP Pocket Reference; What Is HTTP?; HTTP Transactions; Requests; Responses; Parsing the HTML; Structure of HTTP Transactions; Client Methods; GET: Retrieve a Document; HEAD: Retrieve Header Information; POST: Send Data to the Server; URL-encoded format; File uploads with POST; PUT: Store the Entity-Body at the URL; DELETE: Remove URL; TRACE: View the Clients Message Through the Request Chain; OPTIONS: Request Other Options Available for the URL; CONNECT: Proxy Access to Secure Web Servers; Server Response Codes; Informational (100 Range);The HyperText Transfer Protocol, or HTTP, is the backbone of the World Wide Web. HTTP is the language that each web browser (or other web client) uses to communicate with servers around the world. All web programmers, administrators, and application developers need to be familiar with HTTP in order to work effectively.The HTTP Pocket Reference not only provides a solid conceptual foundation of HTTP, it also serves as a quick reference to each of the headers and status codes that comprise an HTTP transaction. The book starts with a tutorial of HTTP, but then explains the client request and server responses in more detail, and gives a thorough technical explanation of more advanced features of HTTP (such as persistent connections and caching).Most people use the Web every day without knowing anything about HTTP, but for those who need to get beyond the browser, this book is the place to start.

HTTP Pocket Reference — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "HTTP Pocket Reference" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make

" name="description"/>

HTTP Pocket Reference
Clinton Wong
Editor
Linda Mui

Copyright 2009 O'Reilly Media, Inc.

OReilly Media Chapter 1 HTTP Pocket Reference This book describes HTTP - photo 1

O'Reilly Media

Chapter 1. HTTP Pocket Reference

This book describes HTTP, the Hypertext Transfer Protocol. Itprovides a high level description of how the protocol works, alongwith reference information on client requests and server responses.Included are dumps of HTTP transactions, as well as tabular data thatsummarizes most of the standardized parameters used in HTTP.

The HTTP Pocket Reference is intended for system administrators, website developers, and software engineers. With an understanding ofHTTP, system administrators will have a better understanding of website configuration and debugging. Web site designers can implementservices that make better use of the protocol and streamline webclient and server interaction. Software engineers who need toimplement HTTP will find this book useful for its short, concisedescription of the protocol.

What Is HTTP?

HTTP is the protocol behind the World Wide Web. With every webtransaction, HTTP is invoked. HTTP is behind every request for a webdocument or graphic, every click of a hypertext link, and everysubmission of a form. The Web is about distributing information overthe Internet, and HTTP is the protocol used to do so.

HTTP is useful because it provides a standardized way for computersto communicate with each other. HTTP specifies how clients requestdata, and how servers respond to these requests. By understanding howHTTP works, you'll be able to:

  • Manually query web servers and receive low-level information thattypical web browsers hide from the user. With this information, youcan better understand the configuration and capabilities of aparticular server, and debug configuration errors with the server orprogramming errors in programs invoked by the web server.

  • Understand the interaction between web clients (browsers, robots,search engines, etc.) and web servers.

  • Streamline web services to make better use of the protocol.

HTTP Transactions

This section presents an example of a common web transaction, showingthe HTTP exchanged between the client and server program.

Requests

Given the following URL:

http://hypothetical.ora.com:80/

The browser interprets the URL as follows:

http://

Use HTTP, the Hypertext Transfer Protocol.

hypothetical.ora.com

Contact a computer over the network with the hostname of hypothetical.ora.com .

:80

Connect to the computer at port 80. The port number can be anylegitimate IP port number: 1 through 65535, inclusively.[] If the colon andport number are omitted, the port number is assumed to beHTTP's default port number, which is 80.

/

Anything after the hostname and optional port number is regarded as adocumentpath. In this example, the document path is /.

So the browser connects to hypothetical.ora.com on port 80 using theHTTP protocol. The message that the browser sends to the server is:

GET / HTTP/1.1Accept: image/gif, image/x-xbitmap, image/ jpeg, image/pjpeg, */*Accept-Language: en-usAccept-Encoding: gzip, deflateUser-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)Host: hypothetical.ora.comConnection: Keep-Alive

Let's look at what these lines are saying:

  1. The first line of this request(GET / HTTP/1.1) requests a document at / from theserver. HTTP/1.1 is given as the version of theHTTP protocol that the browser uses.

  2. The second line tells the server what kind of documents are acceptedby the browser.

  3. The third line indicates that the preferred language is English. Thisheader allows the client to specify a preference for one or morelanguages, in the event that a server has the same document inmultiple languages.

  4. The fourth line indicates that the client understands how tointerpret a server response that is compressed with the gzip ordeflate algorithm.

  5. In the fifth line, beginning with the stringUser-Agent, the client identifies itself asMozilla version 4.0, running on Windows NT. In parenthesis itmentions that it is really Microsoft Internet Explorer version 5.01.

  6. The sixth line tells the server what the client thinks theserver's hostname is.This header is mandatory in HTTP 1.1, but optional in HTTP 1.0. Sincethe server may have multiple hostnames, the client indicates whichhostname is being requested. In this environment, a web server canhave a different document tree for each hostname assigned to it. Ifthe client hasn't specified the server's hostname, theserver may be unable to determine which document tree to use.

  7. The seventh line (Connection:) tells theserver to keep the TCP connection open until explicitly told todisconnect. Under HTTP 1.1, the default server behavior is to keepthe connection open until the client specifies that the connectionshould be closed. The standard behavior in HTTP 1.0 is to close theconnection after the client's request. See the discussion in later in this book for details.

Together, these seven lines constitute a request . Lines twothrough seven are request headers . discusses each header in more detail.

Responses

Given arequest like the one previously shown, the server looks for theserver resource associated with "/" and returns it to thebrowser, preceding it with header information in its response. Theresource associated with the URL depends on how the server isimplemented. It could be a static file or it could be dynamicallygenerated. In this case, the server returns:

HTTP/1.1 200 OKDate: Mon, 06 Dec 1999 20:54:26 GMTServer: Apache/1.3.6 (Unix)Last-Modified: Fri, 04 Oct 1996 14:06:11 GMTETag: "2f5cd-964-381e1bd6"Accept-Ranges: bytesContent-length: 327Connection: closeContent-type: text/htmlSample Homepage
Welcome
Hi there, this is a simple web page. Granted,it may not be as elegant as some other webpages you've seen on the net, but there are some common qualities:
  • An image,
  • Text,
  • and a

If you look at this response, you'll see it begins with aseries of lines that specify information about the document and aboutthe server itself. After a blank line, it returns the document. Lines2-9 are called the response header, and the part after thefirst blank line is called the body or entity, or entity-body.Let's look at the header information:

  1. The first line, HTTP/1.1 200 OK, tells the clientwhat version of the HTTP protocol the server uses. But moreimportantly, by returning a status code of 200, it says that thedocument has been found and will transmit the document in itsresponse.

  2. The second line indicates the current date on the server. The time isexpressed in Greenwich Mean Time (GMT).

  3. The third line tells the client what kind of software the server isrunning. In this case, the server is Apache version 1.3.6 on Unix.

  4. The fourth line specifies the most recent modification time of thedocument requested by the client. Thismodification time is often used for cachingpurposesso a browser may not need to request the entire HTMLfile again if its modification time doesn't change

  5. The fifth line indicates an entity tag. This provides the web clientwith a unique identifier for the server resource. It is highlyunlikely for two different server resources to have the same entitytag. This tag provides a powerful mechanism for caching.

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «HTTP Pocket Reference»

Look at similar books to HTTP Pocket Reference. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «HTTP Pocket Reference»

Discussion, reviews of the book HTTP Pocket Reference and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.