INN commit: branches/2.5/doc/pod (hook-perl.pod news.pod)

INN Commit rra at isc.org
Thu Aug 5 19:51:25 UTC 2010


    Date: Thursday, August 5, 2010 @ 12:51:24
  Author: iulius
Revision: 9098

Mention that Perl and Python filters for innd return the *first* occurrence
of header fields in the %hdr variable.  Whereas it is the *last* occurrence
for the Perl filter for nnrpd.

Modified:
  branches/2.5/doc/pod/hook-perl.pod
  branches/2.5/doc/pod/news.pod

---------------+
 hook-perl.pod |   23 ++++++++++++-----------
 news.pod      |    4 ++++
 2 files changed, 16 insertions(+), 11 deletions(-)

Modified: hook-perl.pod
===================================================================
--- hook-perl.pod	2010-08-05 19:50:44 UTC (rev 9097)
+++ hook-perl.pod	2010-08-05 19:51:24 UTC (rev 9098)
@@ -306,17 +306,18 @@
 the string returned by filter_post() is returned to the client as the
 error message (with some exceptions; see below).
 
-filter_post() has access to a global hash %hdr, which contains all of the
-headers of the article.  (Unlike the innd Perl filter, %hdr for the nnrpd
-Perl filter contains *all* of the headers, not just the standard ones.  If
-any of the headers are duplicated, though, %hdr will contain only the
-value of the last occurrence of the header.  nnrpd will reject the
-article before the filter runs if any of the standard headers are
-duplicated.)  It also has access to the full body of the article in the
-variable $body, and if the poster authenticated via AUTHINFO (or if either
-Perl authentication or a readers.conf authentication method is used and
-produces user information), it has access to the authenticated username of
-the poster in the variable $user.
+filter_post() has access to a global hash C<%hdr>, which contains all
+of the headers of the article.  (Unlike the B<innd> Perl filter, C<%hdr>
+for the B<nnrpd> Perl filter contains *all* of the headers, not just the
+standard ones.  If any of the headers are duplicated, though, C<%hdr>
+will contain only the value of the last occurrence of the header, whereas
+it is the first occurrence with the B<innd> Perl filter.  B<nnrpd> will
+reject the article before the filter runs if any of the standard headers
+are duplicated.)  It also has access to the full body of the article in
+the variable C<$body>, and if the poster authenticated via AUTHINFO (or
+if either Perl authentication or a F<readers.conf> authentication method
+is used and produces user information), it has access to the authenticated
+username of the poster in the variable C<$user>.
 
 Unlike the innd Perl filter, the nnrpd Perl filter can modify the %hdr
 hash.  In fact, if the Perl variable $modify_headers is set to true after

Modified: news.pod
===================================================================
--- news.pod	2010-08-05 19:50:44 UTC (rev 9097)
+++ news.pod	2010-08-05 19:51:24 UTC (rev 9098)
@@ -17,6 +17,10 @@
 overview, were therefore returning an empty field.  The content of the
 first occurrence is now returned, in accordance with RFC 3977.
 
+Perl and Python filters for B<innd> now also properly initialize their
+headers variables with the first occurrence of header fields.  (It is
+still the last occurrence for the Perl filter for B<nnrpd>.)
+
 =item *
 
 B<cnfsheadconf> now properly recognizes continuation lines in




More information about the inn-committers mailing list