This question about Using an extension: More info required
LdapNgPlugin query throws Apache2::RequestIO::print error
Whenever I edit a topic with a LdapNgPlugin query in it, I get the following note in my apache error_log:
[Mon Aug 08 05:37:37 2011] [error] [client <...snip...>] Apache2::RequestIO::print: (103) Software caused connection abort at /srv/www/htdocs/wiki/lib/Foswiki/Engine/Apache.pm line 242, referer: https://<...snip...>?t=1312781520
I tested this using the 'example' query from the Plugin topic:
%LDAP{"(objectClass=person)"
base="(OU=MY,OU=EXAMPLE,OU=COMPANY)"
limit="10"
header="| Nr | Name | Mail | Photo |$n"
format="| $index| $cn | $mail | <img src=\"$jpegPhoto\" alt=\"$cn\" title=\"$cn\" width=\"100px\" /> |"
footer="$n<br/><font color='red'>$count users</font>"
sort="cn"
clear="$mail,$jpegPhoto"
}%
Here's the interesting part if I take the <img> tag out from the format argument, the error no longer shows... any thoughts?
--
HughBlair - 08 Aug 2011
Try
%LDAP{"(objectClass=person)"
base="(OU=MY,OU=EXAMPLE,OU=COMPANY)"
limit="10"
header="| Nr | Name | Mail | Photo |$n"
format=" * $jpegPhoto"
sort="cn"
clear="$jpegPhoto"
}%
to list the output of all
$jpegPhoto
. Then check that the image downloaded and cached from ldap is actually located where it should according to the listed urls. Then access one image directly following one url.
--
MichaelDaum - 09 Aug 2011
Hi Michael,
Actually I think I explained the issue badly. The page renders fine with
bin/view
... it only throws the error when I run
bin/edit
on that topic. The image is located in the path where $jpegPhoto thinks it should be. It just seems to throw the error when an
<img>
tag is there.
To demonstrate (in a weird way) say if I put into the format argument:
format=" * $jpegPhoto %PUBURL%/System/ProjectLogos/foswiki-logo.gif"
then I see no
Apache2::RequestIO::print
error. If I put this in instead:
format=" * $jpegPhoto <img src=\"%PUBURL%/System/ProjectLogos/foswiki-logo.gif\" />"
then I see the
Apache2::RequestIO::print
error.
Actually if I take out the $jpegPhoto reference out completely from the format argument the same thing happens.
I assume there's no actual loss of funtionality so I won't be missing any sleep over this one
--
HughBlair - 11 Aug 2011