Chunked Requests do not work in Iron Framework

[cetra3]

Not sure where the problem lies here but appears that the multipart intercept in iron gets stuck on a chunked boundary.

Not normally an issue if you use this via curl, but the multipart hyper client appears to send it in chunks which is not read correctly by the multipart iron handler.

Steps to test:

• Submit to an iron request with the intercept enabled and a println!("{:?}", entries) statement above the response:

sudo cargo run --features all --example iron_intercept

• Use a client multipart with hyper

Watch the println output of the iron request:

Entries { fields: {}, files: {}, dir: Temp(TempDir { path: "/tmp/multipart.fcIrXAW1ERnN" }) }

Notice that there are no files.

With curl (curl -F "file=@lorem_ipsum.txt" localhost) this works ok:

Entries { fields: {}, files: {"file": SavedFile { path: "/tmp/multipart.GgWgbNoThb1U/kJiP8pJ5MRNr", filename: Some("lorem_ipsum.txt"), size: 5 }}, dir: Temp(TempDir { path: "/tmp/multipart.GgWgbNoThb1U" }) }

[abonander]

I believe that I have resolved this in 0.9.0-alpha.4 as part of various fixes for #51. Try that version and see if it still has a problem.

[cetra3]

@abonander is 0.9.0-alpha.4 released here? Or is it just on crates.io

[abonander]

It is published on crates.io; the source is the httparse branch in this repo.

[cetra3]

@abonander it seems like it's better, i.e, it's finding the file, but I get the following error in the logs:

ERROR:hyper::server: request error = TooLarge

And the checksum of the file doesn't match, it appears to include the newline characters at the end of it (2 extra bytes).

Before Upload

File contents:

A test File

Hex output:

0000000 41 20 74 65 73 74 20 46 69 6c 65 0a            
000000c

After Upload

File contents:

A test File

Hex output:

0000000 41 20 74 65 73 74 20 46 69 6c 65 0a 0d 0a      
000000e

[abonander]

@cetra3 Try with multipart = "0.9.0-alpha.5". I've rewritten a lot of the boundary parsing, it shouldn't ever allow those extra newline characters.

[abonander]

Ping @cetra3, I'm waiting for your response (and someone else's) before I publish 0.9.0.

[Boscop]

With 0.8.1 I'm always getting "Unexpected 2-bytes after boundary: [0, 0]" when trying to upload images as part of a form like this.

[abonander]

@Boscop Try multipart = "0.9.0-alpha.9", there's a lot of bugfixes that are almost ready for a full release.

[Boscop]

I'm using the params crate which depends on multipart 0.8.1. So I can't use [replace] to use a different version...

[abonander]

@Boscop You can try cloning params locally and updating the multipart version but I'll probably just go ahead and publish a release version and ask them to update.