RE: Multipart tests

> > then the service works. But I think the check-multipart service should
> > ignore any data before first boundary string, as MIME-compliant
> > clients should do.
> 
> Fixed, I think. Please let me know.

It only works when the boundary is not quoted in the content-type header. At the moment, Calumet is quoting the boundary string by default. But I can change that, unless you want to fix the service :)

> Yeah. I'm not sure how to parse the iso-8859-2 text in my little Perl
> progam. Especially not without a content-length to tell me how long it
> is.

ISO-8859-2 is a simple single-byte encoding. But I wouldn't really bother about this in the service. 

> > 3. The expected result for the multipart tests is:
> >
> > <check-multipart
> > boundary="aaaabbbbccccddddeeefffggghhhiiijjjkkkllmmmnop"
> > content-type="multipart/mixed"> ... </check-multipart>
> >
> > However, what I always get from the check-multipart service is this:
> >
> > <check-multipart
> > boundary="aaaabbbbccccddddeeefffggghhhiiijjjkkkllmmmnop"
> > content-type="multipart/mixed;
> > boundary=aaaabbbbccccddddeeefffggghhhiiijjjkkkllmmmnop"> ...
> > </check-multipart>
> >
> > In other words, the boundary is included in the value of the
> > content-type attribute. I am actually surprised you don't get the
> > boundary string in the content-type attribute with Calabash as you
> > must (at least I think) be sending the boundary in the Content-Type
> > header of the multipart message.
> 
> Yeah, I got that totally wrong :-)

OK, so you are now removing boundary from the content-type. Just checking that what I see is correct.

Vojtech

Received on Thursday, 25 February 2010 13:59:24 UTC