[SM-PLUGINS] Next question... possible header corruption?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Look at these two headers:<br>
<tt>X-Face: 'HVkL'h@jz#Ba_9R&amp;5w3^'$Z&gt;Zjf;<br>
&nbsp;&nbsp;&nbsp;&nbsp;
l)'"$)TCfZ/UGu$tA@HwGXl2z"_@V0qpT[o)U'1q9WxgclT^l:6(@`ry-a5jjicT#U3Yn#<br>
&nbsp;&nbsp;&nbsp;&nbsp; IGQ,sb=[g/?%ulNyTYhsY}KaqyNjI'8ZPC}]vI,+{Uf,<br>
&nbsp;&nbsp;&nbsp;&nbsp;
+US4tS^cVg|2qm9B[vlVyi^`'4gAnBC]FY1:)Cxbs\Cr&lt;+g@21L,fu]tceV1Yn;)QE,<br>
&nbsp;&nbsp;&nbsp;&nbsp; ;+=cG#}$z^_@a&lt;tu]&lt;}@zuKM~BL_PPG*Vluk;EJfs1k3&amp;{<br>
Face:<br>
&nbsp;&nbsp;&nbsp;&nbsp;
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEX/39LLn5VYR0QpJy<br>
&nbsp;&nbsp;&nbsp;&nbsp;
mDZV8SExMFBwZsSkHdAAACKklEQVQ4jVWUXa7cIAyFyQ6CxAI6BvX9hiTPA2UFpbCARrD/<br>
&nbsp;&nbsp;&nbsp;&nbsp;
JfTYkMwt0mQiPvxzbBNFRBt+1m/++wpqvhyldF6lyl/flcWuxWlstNru/f5HALs5sFue/f<br>
&nbsp;&nbsp;&nbsp;&nbsp;
5bALGv3srx7E+w4YHjBY86jSbwmR1WoFxq/YA7sSx2/wGSp9h5AX8BDgSQlPECof5okHQp<br>
&nbsp;&nbsp;&nbsp;&nbsp;
KMvsBBlvlFIi8mWCmo/sX3quRJZrcKkT4MxuVVgTHGJxcinyezFJrwIQtE6L3r9w2KSA/c<br>
&nbsp;&nbsp;&nbsp;&nbsp;
h5DVec3Y9FTq/aRPTAD4teGcBH0mpJlMgPcKAH/b2kEFNQSxSp50gXrt7K4OyLgR9BxFUF<br>
&nbsp;&nbsp;&nbsp;&nbsp;
UBwcwKLSm/24EhErx6CIAWCASKUJgMaFSzKBdO0tugdwKdpZq96DGmtJEXWMto7qTqBvMG<br>
&nbsp;&nbsp;&nbsp;&nbsp;
OwnBefZmAipenKshwGJgzgPuCqX8jUICudHNF0Zb296r4qzXFMdE+6vzZ79V2jiqw+0jfg<br>
&nbsp;&nbsp;&nbsp;&nbsp;
CwDrVty/B2AsatuC9NskWLj0AT1jFkzQBk3yzjzg7NkhhEagZCmIRWOAOdk5hoE2ciHSz2<br>
&nbsp;&nbsp;&nbsp;&nbsp;
mBeUWQdZQwukjnBCgXBo41oo3cjjpc4S4hJIIgBDujow8L7qEA1gFgb4B0W3ZhXQVg3nsf<br>
&nbsp;&nbsp;&nbsp;&nbsp;
ZYdJaf6lhgWN+8EAlyMXTKniqYskBuzqKJiXkrnAUit/fwDK5XeMONfRmBm670HxNQmJK4<br>
&nbsp;&nbsp;&nbsp;&nbsp;
UawsBCXW8vzaCtrAFXgD81VkbaAdR+rOM2GQwo7uHZ6oVx5UP3PUvcDUNBw+8/VPf66kdP<br>
&nbsp;&nbsp;&nbsp;&nbsp; 4S8AAAAASUVORK5CYII=</tt><br>
<br>
The obvious thing with the first header is that apparently SM breaks
the line at commas? I don't necessarily think it's a problem, but it
sure looks odd :)<br>
<br>
The problem with the second line however is a bit more worrisome. For
some bizarre reason SM inserts a line break between the header name and
the actual header content. As near as I can tell it's got to do with
the length of the header. The code that produces these headers is
simple:<br>
<br>
<tt>function xface_compose_send_addheader(&amp;$argv) {<br>
&nbsp; $pref_xface =
trim(getPref($data_dir,$username,'plugin_xface_xfaceicon', ''));<br>
&nbsp; $pref_face =
trim(getPref($data_dir,$username,'plugin_xface_faceicon', ''));<br>
&nbsp; <br>
&nbsp; $message[0]=&amp;$argv[0];<br>
&nbsp; $message[1]=&amp;$argv[1];<br>
&nbsp; if(strlen($pref_xface)&gt;0)
$message[1]-&gt;rfc822_header-&gt;more_headers["X-Face"] = $pref_xface;<br>
&nbsp; if(strlen($pref_face)&gt;0)
$message[1]-&gt;rfc822_header-&gt;more_headers["Face"] = $pref_face;<br>
&nbsp; <br>
&nbsp; return($message);<br>
}</tt><br>
<br>
If I look at the config file (where both strings are stored), they both
look perfectly fine. The headers BOTH still seem to work in every
client I tried, so it either doesn't violate RFC or the clients are
rather tolerant :) Anyway... just thought I'd point it out.<br>
<br>
J<br>
</body>
</html>