mime-multipart-hyper1 0.10.0

MIME multipart parsing, construction, and streaming compatible with hyper v1.x (fork of mime_multipart crate)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# mime-multipart-hyper1

[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE-MIT)
[![Apache-2.0 licensed](https://img.shields.io/badge/license-APACHE2-blue.svg)](./LICENSE-APACHE)

Rust library for MIME multipart parsing, construction, and streaming compatible with hyper v1.x

This is a fork of https://github.com/mikedilger/mime-multipart with support for newer hyper versions.

Documentation is available at https://docs.rs/mime-multipart-hyper1

## Compatibility

* **Version 0.8**
  * Use Rust version 2021
  * Update hyper from 0.10 to 0.11
  * Updates mime crate to version 0.3 (up-to-date at time of writing, November 2024)
* **Version 0.9**
  * Update hyper to 0.14 (also compatible with hyper 0.12 and 0.13)
* **Version 0.10**
  * Replace hyper dependency with http crate. This makes this crate compatible with hyper 1.x

## Features

* Parses from a stream, rather than in memory, so that memory is not hogged.
* Streams parts which are identified as files (via the part's Content-Disposition header,
  if any, or via a manual override) to files on disk.
* Uses buffered streams.
* Lets you build and stream out a multipart as a vector of parts (`Node`s), some of which
  could be files, others could be nested multipart parts.

If you are specifically dealing with `multipart/formdata`, you may be interested in
https://github.com/mikedilger/formdata which uses this crate and takes it a step
further.

## License

Licensed under either of

* Apache License, Version 2.0
  ([LICENSE-APACHE](LICENSE-APACHE)
  or http://www.apache.org/licenses/LICENSE-2.0)
* MIT license
  ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall
be dual licensed as above, without any additional terms or conditions.