in reply to Trouble with Autoresponder Perl Script

This is not really great code. If you wrote this yourself, I recommend starting over. Good starting points would be to remove all the HTML generation and putting the HTML into separate files. If you did not write this code yourself, I recommend contacting support of whoever wrote this code.

If you want to track down the real issue, the problem seems to be that somewhere in the code, something outputs an HTTP header that contains a newline. This should never happen. Find out why it happens and eliminate the cause.

Note: This node was changed to ameliorate the harsh tone.

  • Comment on Re: Trouble with Autoresponder Perl Script

Replies are listed 'Best First'.
Re^2: Trouble with Autoresponder Perl Script
by jeffa (Bishop) on Mar 24, 2015 at 18:14 UTC

    Actually, i am inclined to believe the problem might lie somewhere outside this code ... namely in the imported file 'conf.cgi'. Notice that the OP has several functions attached to keys in the dispatch table that are not even in this code:

    • &print_frameset
    • &print_account
    • &print_manage_signatures
    • &openXinha
    • &print_main
    • &print_getfile
    • &print_delfile
    • &print_doimess
    • &print_subsmess
    • &print_unsubsmess
    • &print_show_mess
    • &print_show_rfc_mess
    • &print_change_editor
    • &print_test_send
    • &print_statdaily
    • &print_logout
    Any one of those could potentially be outputting the invalid HTTP header.

    UPDATE: oops! ... i just now noticed that the code was truncated. Perhaps those functions are defined in the same body of code. Either way ... it's a mess to trudge through.

    jeffa

    L-LL-L--L-LL-L--L-LL-L--
    -R--R-RR-R--R-RR-R--R-RR
    B--B--B--B--B--B--B--B--
    H---H---H---H---H---H---
    (the triplet paradiddle with high-hat)