GOOGLE | CHEAT SHEET
This two page Google Cheat Sheet lists all Google services and tools as
well as background information. The Cheat Sheet offers a great reference
to grasp of basic to advance Google query building concepts and ideas.
Jumat, 02 Mei 2008
Kamis, 01 Mei 2008
eBook Hacking, Programming dan yang Berkaitan dengan Komputer
eBook Hacking, Programming dan yang Berkaitan dengan Komputer
HTTP Errors
HTTP Errors
100 Continue101 Switching Protocols
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
303 See Other
304 Not Modified
305 Use Proxy
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Time-Out
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Out of Resources
504 Gateway Time-Out
505 HTTP Version not supported
HTTP Info
HTTP Info
| Method | Description |
| GET | means retrieve whatever data is identified by the URI, so where the URI refers to a data-producing process, or a script which can be run by such a process, it is this data which will be returned, and not the source text of the script or process. Also used for searches. |
| HEAD | is the same as GET but returns only HTTP headers and no document body. |
| CHECKOUT | is similar to GET but locks the object against update by other people. The lock may be broken by a higher authority or on timeout: in this case a future CHECKIN will fail. (Phase out?) |
| SHOWMETHOD | returns a description (perhaps a form) for a given method when applied to the given object. The method name is specified in a For-Method: field. (TBS) |
| PUT | specifies that the data in the body section is to be stored under the supplied URL. The URL must already exist. The new contenst of the document are the data part of the request. POST and REPLY should be used for creating new documents. |
| DELETE | requests that the server delete the information corresponding to the given URL. After a successfull DELETE method, the URL becomes invalid for any future methods. |
| POST | creates a new object linked to the specified object. The message-id field of the new object may be set by the client or else will be given by the server. A URL will be allocated by the server and returned to the client. The new document is the data part of the request. It is considered to be subordinate to the specified object, in the way that a file is subordinate to a directory containing it, or a news article is subordinate to a newsgroup to which it is posted. |
| LINK | links an existing object to the specified object. |
| UNLINK | removes link (or other meta-) information from an object. |
| CHECKINv | is similar to PUT, but releases the lock set on the object. Fails if no lock has been set by CHECKOUT. Suggestion : phase out this (rcs-like) model in favor of the PUT (cvs-like, non-locking) model of code management. |
| TEXTSEARCH | the object may be queried with a text string. The search form of the GET method is used to query the object. |
| SPACEJUMP | the object will accept a query whose terms are the cooridnates of a point within the object. The method is implemented using GET with a derived URL. |
| SEARCH | proposed only, the index (etc) identified by the URL is to be searched for something matching in some sense the enclosed message. How does the client know what message fromats are acceptable to the server? (Suggestion of Fred Williams) |
| CONNECT | creates an end-to-end tunnel between two machines through a proxy/firewall machine. |
| BCOPY BDELETE BMOVE BPROPFIND BPROPPATCH COPY DELETE LOCK MKCOL MOVE NOTIFY POLL PROPFIND PROPPATCH SEARCH SUBSCRIBE UNLOCK UNSUBSCRIBE X-MS-ENUMATTS | WebDAV Methods |
Langganan:
Postingan (Atom)
