Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.apache.commons.httpclient.methods.multipart.* (8)

org.apache.commons.httpclient.methods: Javadoc index of package org.apache.commons.httpclient.methods.


Package Samples:

org.apache.commons.httpclient.methods.multipart: Classes implementing org.apache.commons.httpclient.HttpMethod     for the base HTTP methods.  

Classes:

MultipartRequestEntity: Implements a request entity suitable for an HTTP multipart POST method. The HTTP multipart POST method is defined in section 3.3 of RFC1867 : The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in RFC 1521. The multipart/form-data contains a series of parts. Each part is expected to contain a content-disposition header where the value is "form-data" and a name attribute specifies the field name within the form, e.g., 'content-disposition: form-data; name="xxxxx"', where xxxxx is the field name corresponding to that field. Field names originally in ...
ExpectContinueMethod: This abstract class serves as a foundation for all HTTP methods that support 'Expect: 100-continue' handshake. The purpose of the 100 (Continue) status (refer to section 10.1.1 of the RFC 2616 for more details) is to allow a client that is sending a request message with a request body to determine if the origin server is willing to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking at the body. 'Expect: ...
PostMethod: Implements the HTTP POST method. The HTTP POST method is defined in section 9.5 of RFC2616 : The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the following functions: Annotation of existing resources Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles Providing a block of data, such as the result of submitting a form, to a data-handling process Extending a database through ...
MultipartPostMethod: Implements the HTTP multipart POST method. The HTTP multipart POST method is defined in section 3.3 of RFC1867 : The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in RFC 1521. The multipart/form-data contains a series of parts. Each part is expected to contain a content-disposition header where the value is "form-data" and a name attribute specifies the field name within the form, e.g., 'content-disposition: form-data; name="xxxxx"', where xxxxx is the field name corresponding to that field. Field names originally in non-ASCII character sets may ...
HeadMethod: Implements the HTTP HEAD method. The HTTP HEAD method is defined in section 9.4 of RFC2616 : The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification.
GetMethod: Implements the HTTP GET method. The HTTP GET method is defined in section 9.3 of RFC2616 : The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process. GetMethods will follow redirect requests from the http server by default. This behavour can be disabled by calling setFollowRedirects(false).
TraceMethod: Implements the HTTP TRACE method. The HTTP TRACE method is defined in section 9.6 of RFC2616 : The TRACE method is used to invoke a remote, application-layer loop- back of the request message. The final recipient of the request SHOULD reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see section 14.31). A TRACE request MUST NOT include an entity.
OptionsMethod: Implements the HTTP OPTIONS method. The HTTP OPTIONS method is defined in section 9.2 of RFC2616 : The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
PutMethod: Implements the HTTP PUT method. The HTTP PUT method is defined in section 9.6 of RFC2616 : The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server.
DeleteMethod: Implements the HTTP DELETE method. The HTTP DELETE method is defined in section 9.7 of RFC2616 : The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method MAY be overridden by human intervention (or other means) on the origin server.
ByteArrayPartSource: A PartSource that reads from a byte array. This class should be used when the data to post is already loaded into memory.
UrlGetMethod: Implements the URL version of GetMethod. It serves the same purpose as GetMethod but it takes URL instead of a path.
EntityEnclosingMethod: This abstract class serves as a foundation for all HTTP methods that can enclose an entity within requests
FilePart: This class implements a part of a Multipart post object that consists of a file.
PartSource: An interface for providing access to data when posting MultiPart messages.
PartBase: Provides setters and getters for the basic Part properties.
Part: Abstract class for one Part of a multipart post object.
ByteArrayRequestEntity: A RequestEntity that contains an array of bytes.
InputStreamRequestEntity: A RequestEntity that contains an InputStream.
StringPart: Simple string parameter for a multipart post
UrlOptionsMethod: HttpUrlMethod version of Options method.
StringRequestEntity: A RequestEntity that contains a String.
UrlDeleteMethod: HttpUrlMethod version of DeleteMethod.
UrlHeadMethod: HttpUrlMethod version of HeadMethod.
UrlPostMethod: HttpUrlMethod version of PostMethod.

Home | Contact Us | Privacy Policy | Terms of Service