It's a perfectly reasonable sort of trap to fall into. I would just point out that you could have debugged it at the client side, simply by printing that same output to a local file or to stdout instead of (or in addition to) sending it to the socket.

If you had done that sort of test before adding the extra parameter to the string, you might have noticed the extra line-feed in the output, and wondered about that -- maybe it would have no effect on what happens at the server end, but I can easily imagine some situations where an extra line-feed (i.e. a blank line) going through the socket could have an effect, which might be bad.

In reply to Re: beware of the newline at the end of the encode_base64-encoded strings by graff
in thread Beware of the newline at the end of the encode_base64() encoded strings by kirillm

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.