Brian Ipsen <[EMAIL PROTECTED]> writes: > Today I received a message, which causes tmda-cgi (0.11B) to fail when > trying to preview it. Actually, I get an HTTP error (internal server > error) - it could be because the message is malformed, but could someone > please take a looke at it ??
Well, the message is definitely malformed, but the broken part doesn't really matter because it's not used. Very strange. > My http log says: > > [Sun Feb 8 14:32:14 2004] [error] [client 192.168.1.101] malformed header > from script. Bad header= boundary="----=_nextpart_000_: > /home/httpd/cgi-bin/tmda.cgi This I don't understand. The broken part of the message is, indeed the Content-Type field; the type is ok (text/html) but the charset and boundary parameters aren't separated by a semi-colon. The boundary paramater begins on the second line of the field but that is perfectly legal, as long as the second (and following) lines of any given field begin with a space or tab. The line containing the boundary parameter does begin with a space. The above message looks like your webserver is trying to interpret the boundary parameter as an HTTP header field, which doesn't make any sense to me, given that 1) it occurs after numerous other email header fields that are (apparently) accepted as regular output from tmda-cgi and 2) it starts with a space, which should mean that your webserver doesn't look at it. I don't really have any way to figure out anything more.... Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
