It was in something I read somewhere regarding the REST interface. Maybe it was in the wiki and someone else wrote it.
-- Tom Lahti, SCMDBA, LPIC-1, CLA BIT LLC 425-251-0833 x 117 >> I've filed a bug report. >> http://issues.bestpractical.com/Ticket/Display.html?id=16418 >> >> This is probably the 3rd time its come up. I've discussed it with Jesse on >> the RT user's list and he recommended filing a bug report the last time it >> came up. The problem isn't really with rt-client, its with RT. This >> non-compliance with RFC 822 when that was intended will cause not only >> rt-client to fail, but other similar libraries as well that use a 3rd party >> RFC 822 parser. Having a space in the field name of an RFC 822 header is >> not compliant with the RFC. > > I don't think we've ever claimed to be RFC 822 compliant. Have we?
smime.p7s
Description: S/MIME cryptographic signature
