RE: POST method

> From: Irfan Akber [SMTP:irfan@inet.com.pk]
>
> I am writing a small proxy server. How does POST works so that I can
> include that in my proxy server. It works for GET but with POST it fails.
>
        POST sends the body of the transmission, which should have
        similar content type headers to a response, to the server
        to, in some sense, be added to the named resource (e.g. new
        inputs from a form, or a mail message to send). PUT creates
        or replaces the named resource.

        POSTs are assumed to make a significant change in the state of
        the server, which need not be idempotent, i.e. if you post two
        orders, your account can get debitted twice.

        The server then returns a reponse in a similar way to a get.
        It can return a redirect, but many early clients misinterpreted
        this as being redirect to get another page when it actually
        meant re-POST to the new resource. There are now multiple
        types of redirect to try to cover these cases.

> Which rfc should I read for this ?
>
        You should follow the links on www.w3c.org to the latest
        HTTP internet draft. The last published RFC was 2068, but
        is now out of date. This is absolutely essential reading for
        any proxy server writer. It is not a small document (115pp).

        Technically you shouldn't implement products against drafts, but
        ....
Received on Fri Jun 04 1999 - 06:37:17 MDT