Package org.jboss.netty.handler.codec.http.multipart
HTTP multipart support.
-
Interface Summary Interface Description Attribute Attribute interfaceFileUpload FileUpload interface that could be in memory, on temporary file or any other implementations.HttpData Extended interface for InterfaceHttpDataHttpDataFactory Interface to enable creation of InterfaceHttpData objectsInterfaceHttpData Interface for all Objects that could be encoded/decoded using HttpPostRequestEncoder/DecoderInterfaceHttpPostRequestDecoder -
Class Summary Class Description AbstractDiskHttpData Abstract Disk HttpData implementationAbstractHttpData Abstract HttpData implementationAbstractMemoryHttpData Abstract Memory HttpData implementationDefaultHttpDataFactory 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 AttributesDiskFileUpload Disk FileUpload implementation that stores file into real filesHttpPostMultipartRequestDecoder This decoder will decode Body and can handle POST BODY in multipart form.HttpPostRequestDecoder This decoder will decode Body and can handle POST BODY (both multipart and standard).HttpPostRequestEncoder This encoder will help to encode Request for a FORM as POST.HttpPostStandardRequestDecoder This decoder will decode Body and can handle standard (non multipart) POST BODY.InternalAttribute This Attribute is only for Encoder use to insert special command between object if needed (like Multipart Mixed mode)MemoryAttribute Memory implementation of AttributesMemoryFileUpload Default FileUpload implementation that stores file into memory.
Warning: be aware of the memory limitation.MixedAttribute Mixed implementation using both in Memory and in File with a limit of sizeMixedFileUpload Mixed implementation using both in Memory and in File with a limit of size -
Enum Summary Enum Description HttpPostRequestDecoder.MultiPartStatus states follow NOTSTARTED PREAMBLE ( (HEADERDELIMITER DISPOSITION (FIELD | FILEUPLOAD))* (HEADERDELIMITER DISPOSITION MIXEDPREAMBLE (MIXEDDELIMITER MIXEDDISPOSITION MIXEDFILEUPLOAD)+ MIXEDCLOSEDELIMITER)* CLOSEDELIMITER)+ EPILOGUE First status 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 ...HttpPostRequestEncoder.EncoderMode Different modes to use to encode form data.InterfaceHttpData.HttpDataType -
Exception Summary Exception Description HttpPostRequestDecoder.EndOfDataDecoderException Exception when the body is fully decoded, even if there is still dataHttpPostRequestDecoder.ErrorDataDecoderException Exception when an error occurs while decodingHttpPostRequestDecoder.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