| tag | 59c502a4071ebb9ee0f54fb67af3c5a1a4ffb5c4 | |
|---|---|---|
| tagger | Kevin Moore <kevmoo@google.com> | Tue May 15 20:28:12 2018 |
| object | aac2d8d41f75775155a0e42b0a932d28ee5ee746 |
| commit | aac2d8d41f75775155a0e42b0a932d28ee5ee746 | [log] [tgz] |
|---|---|---|
| author | Lasse R.H. Nielsen <lrn@google.com> | Fri May 04 09:46:37 2018 |
| committer | GitHub <noreply@github.com> | Fri May 04 09:46:37 2018 |
| tree | afe2429f6bed73f3e83d40b1f22475ca017c3b81 | |
| parent | e8574ad5f428fafef10e5f39329d0c1e89fcbc05 [diff] |
Remove upper case constants (#17) Remove usage of upper-case constants. Update SDK version.
Package for working with MIME type definitions and for processing streams of MIME multipart media types.
The MimeTypeResolver class can be used to determine the MIME type of a file. It supports both using the extension of the file name and looking at magic bytes from the beginning of the file.
There is a builtin instance of MimeTypeResolver accessible through the top level function lookupMimeType. This builtin instance has the most common file name extensions and magic bytes registered.
print(lookupMimeType('test.html')); // Will print text/html print(lookupMimeType('test', [0xFF, 0xD8])); // Will print image/jpeg print(lookupMimeType('test.html', [0xFF, 0xD8])); // Will print image/jpeg
You can build you own resolver by creating an instance of MimeTypeResolver and adding file name extensions and magic bytes using addExtension and addMagicNumber.
The class MimeMultipartTransformer is used to process a Stream of bytes encoded using a MIME multipart media types encoding. The transformer provides a new Stream of MimeMultipart objects each of which have the headers and the content of each part. The content of a part is provided as a stream of bytes.
Below is an example showing how to process an HTTP request and print the length of the content of each part.
// HTTP request with content type multipart/form-data. HttpRequest request = ...; // Determine the boundary form the content type header String boundary = request.headers.contentType.parameters['boundary']; // Process the body just calculating the length of each part. request .transform(new MimeMultipartTransformer(boundary)) .map((part) => part.fold(0, (p, d) => p + d)) .listen((length) => print('Part with length $length'));
Take a look at the HttpBodyHandler in the http_server package for handling different content types in an HTTP request.
Please file feature requests and bugs at the issue tracker.