You might want to submit your report along with a recommended patch, if you want to get it implemented quicker.

I second that, whole-heartedly. In fact, here's my suggestion for a better version (hoping I understand the intent correctly):

sub raw_fetch {
   my $class = shift;
   my $raw_cookie = get_raw_cookie(@_) or return;
   my %results;

   $raw_cookie =~ s/^\s+//;
   $raw_cookie =~ s/\s+$//;
   my(@pairs) = split(/\s*;\s*/,$raw_cookie);
   foreach (@pairs) {
     my ($key,$val) = (/^([^=]+)=?(.*)/);
     $results{$key} = $val;
   }
   return \%results unless wantarray;
   return %results;
}
[download]

I've only tested it to the extent that the assignments to %results match the original code (except for the trailing whitespace glitch) -- that is, a "raw_cookie" string like this:

one=1 ;two=2; three=the third ; four=  ; five  ; six = the sixth ;

produces these key/value pairs:

'one'=>'1',
'two'=>'2',
'three'=>'the third',
'four'=>'',
'five'=>'',
'six '=>' the sixth'

(note that spaces next to "=" are not deleted)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.