| 接口 | 说明 |
|---|---|
| Attribute |
Attribute interface
|
| FileUpload |
FileUpload interface that could be in memory, on temporary file or any other implementations.
|
| HttpData |
Extended interface for InterfaceHttpData
|
| HttpDataFactory |
Interface to enable creation of InterfaceHttpData objects
|
| InterfaceHttpData |
Interface for all Objects that could be encoded/decoded using HttpPostRequestEncoder/Decoder
|
| InterfaceHttpPostRequestDecoder |
This decoder will decode Body and can handle POST BODY.
|
| 类 | 说明 |
|---|---|
| AbstractDiskHttpData |
Abstract Disk HttpData implementation
|
| AbstractHttpData |
Abstract HttpData implementation
|
| AbstractMemoryHttpData |
Abstract Memory HttpData implementation
|
| DefaultHttpDataFactory |
Default factory giving Attribute and FileUpload according to constructor
Attribute and FileUpload could be :
- MemoryAttribute, DiskAttribute or MixedAttribute - MemoryFileUpload, DiskFileUpload or MixedFileUpload according to the constructor. |
| DiskAttribute |
Disk implementation of Attributes
|
| DiskFileUpload |
Disk FileUpload implementation that stores file into real files
|
| HttpPostMultipartRequestDecoder |
This decoder will decode Body and can handle POST BODY.
|
| HttpPostRequestDecoder |
This decoder will decode Body and can handle POST BODY.
|
| HttpPostRequestEncoder |
This encoder will help to encode Request for a FORM as POST.
|
| HttpPostStandardRequestDecoder |
This decoder will decode Body and can handle POST BODY.
|
| MemoryAttribute |
Memory implementation of Attributes
|
| MemoryFileUpload |
Default FileUpload implementation that stores file into memory.
|
| MixedAttribute |
Mixed implementation using both in Memory and in File with a limit of size
|
| MixedFileUpload |
Mixed implementation using both in Memory and in File with a limit of size
|
| 枚举 | 说明 |
|---|---|
| HttpPostRequestDecoder.MultiPartStatus |
states follow NOTSTARTED PREAMBLE ( (HEADERDELIMITER DISPOSITION (FIELD |
FILEUPLOAD))* (HEADERDELIMITER DISPOSITION MIXEDPREAMBLE (MIXEDDELIMITER
MIXEDDISPOSITION MIXEDFILEUPLOAD)+ MIXEDCLOSEDELIMITER)* CLOSEDELIMITER)+
EPILOGUE
First getStatus is: NOSTARTED
Content-type: multipart/form-data, boundary=AaB03x => PREAMBLE in Header
--AaB03x => HEADERDELIMITER content-disposition: form-data; name="field1"
=> DISPOSITION
Joe Blow => FIELD --AaB03x => HEADERDELIMITER content-disposition:
form-data; name="pics" => DISPOSITION Content-type: multipart/mixed,
boundary=BbC04y
--BbC04y => MIXEDDELIMITER Content-disposition: attachment;
filename="file1.txt" => MIXEDDISPOSITION Content-Type: text/plain
... contents of file1.txt ... => MIXEDFILEUPLOAD --BbC04y =>
MIXEDDELIMITER Content-disposition: file; filename="file2.gif" =>
MIXEDDISPOSITION Content-type: image/gif Content-Transfer-Encoding:
binary
...contents of file2.gif... => MIXEDFILEUPLOAD --BbC04y-- =>
MIXEDCLOSEDELIMITER --AaB03x-- => CLOSEDELIMITER
Once CLOSEDELIMITER is found, last getStatus is EPILOGUE
|
| HttpPostRequestEncoder.EncoderMode |
Different modes to use to encode form data.
|
| InterfaceHttpData.HttpDataType |
| 异常错误 | 说明 |
|---|---|
| HttpPostRequestDecoder.EndOfDataDecoderException |
Exception when the body is fully decoded, even if there is still data
|
| HttpPostRequestDecoder.ErrorDataDecoderException |
Exception when an error occurs while decoding
|
| HttpPostRequestDecoder.IncompatibleDataDecoderException |
Exception when an unappropriated getMethod was called on a request
|
| HttpPostRequestDecoder.NotEnoughDataDecoderException |
Exception when try reading data from request in chunked format, and not
enough data are available (need more chunks)
|
| HttpPostRequestEncoder.ErrorDataEncoderException |
Exception when an error occurs while encoding
|