It seems that perl's tainting facility could be put to use here. How about a PerlIO layer which prevents you from writing out tainted data? 
#!perl -T

package PerlIO::via::TaintCheck;

sub PUSHED { bless [], $_[0] }
sub WRITE {
  my ($obj, $buf, $fh) = @_;
  if (is_tainted($buf)) { die "attempting to output tainted data" }
  print $fh $buf;
  length $buf;
}

sub is_tainted { # borrowed from PHOENIX/Taint-0.09
    local(@_, $@, $^W) = @_;  # Prevent errors, stringifying
    not eval { join("",@_), kill 0; 1 };
}

package main;

use CGI qw(:standard);

binmode STDOUT, ':via(TaintCheck)';
...
# catch insecure use of param data:
print "<p>Welcome, ", param('name'), ", to our web site.\n";

[download]

In reply to Re: HTTP Response splitting by pc88mxer
in thread HTTP Response splitting by narainhere

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.