RE: A question on the HTML verbs GET and POST



for complete inforation read: http://www.rfc-editor.org/rfc/rfc2616.txt
in summary a http request has three parts:

1) a request verb and uri
2) a list of headers
3) in the case of a post, content


there are serveral verbs (here are the most common)

HEAD - retrieve just the headers for a uri
GET - retrieve headers and content for a uri
POST - retrieve headers and content for a uri but content is included (the
content-type header defines the format of the content) following the request
headers

a GET uri request can be for a directory (with IIS enable directory
browsing), in which case the webserver shoudl return a list of files. the
format is not defined, but usually is a list of links.

don't confuse this with IIS defualt documnent, this is handled by the
webserver sending a redirect toanother URI.

with webdav, the webserver can be a file server. to create a document, you
just post it.

-- bruce (sqlwork.com)


"Marc" wrote:

Dear people,

I am studying for 70-528 and in the self paced training kit written by Glenn
Johnson at chapter one I find a list of HTML verbs and their description. If
possible I would like to submit a posting here to clearify a few things I do
not understand.

<text in the book>
GET : Gets a URL from the server. A GET request for a specific URL,
say, /test.htm, retrieves the test.htm file. Data retrieved using this verb
is typically cached by the browser. GET also works with collections, such as
those in directories that contain collections of files. If you request a
directory, the server can be configured to return a default file, such as
index.html, that may be representative of the directory.
</text in the book>


I do not understand the part: GET also works with collections, such as
those in directories that contain collections of files.

What does it mean? GET can transfer a bunch of files from the server to the
browser somehow? If that's it, what is this used for, since I have never
seen it.

<text in the book>
POST : Used to create a new, dynamically named resource. Data retrieved
using this verb is typically not cached.
</text in the book>

I don't get this. I know POST just from posting a form and its content. What
is the 'dynamically named resource'?



.



Relevant Pages

  • Please help !! Apache webserver beeing heavily attacked !!
    ... request |$ʧͯƍ 5 ... failed: error reading the headers ... URI in request Jc_ԺY8R ...
    (comp.os.linux.security)
  • Re: Modifying and posting uri
    ... browser's uri that the user see's but also redirect the uri to something ... The URI in the browser is what the browser uses to request the page. ... Controller which then takes the value of this URI, ... content already is, BUT your Views, the html that you want to be ...
    (comp.lang.php)
  • Re: Java Factory Handler
    ... An incoming request for a specific resource, identified by an URI, ... public String getHandler ... The string array 'config' contains URI patterns and handler names. ...
    (comp.lang.java.programmer)
  • Java Factory Handler
    ... An incoming request for a specific resource, identified by an URI, ... public String getHandler ... The string array 'config' contains URI patterns and handler names. ...
    (comp.lang.java.programmer)
  • Re: Get and Post
    ... Various headers may follow the initial ... programs that handled URI info over the years. ... That search engines make big use of URI extra data is exactly why they ...
    (comp.programming)