[Vortex] error in assumptions about MIME header format

Sam Roberts sroberts at uniserve.com
Tue Aug 28 07:52:26 CEST 2007

Quoting francis at aspl.es, on Mon, Aug 27, 2007 at 09:09:10AM +0200:
> > I understand vortex doesn't have a full MIME parser in it, but I
> > think it should support at some of the common MIME variations.
> > Currently, it assumes "Content-Type: " introduces a content-type
> > header, but MIME specifies case-insensitive matching of header names
> > (via ref to RFC822), allows zero or no whitespace before and after
> > the :, and also specifies that media type/subtype comparisons are
> > case-insensitive (sec 5.1, rfc2045).
> You are right Sam, though it is a temporal situation. We opted
> implementing this minimal MIME support using the common case to focus
> in other areas in Vortex, but a full MIME parser it is required [1]...

axl_casecmp() might be enough to get you a long way.

I changed beepy to use Content-Type, as vortex assumes it must be, and
now the communicate, but it is worrisome, if I run into another
implementation with this problem, but that assumes "content-type" things
will not go well.


More information about the Vortex mailing list