in reply to Re^2: CGI Header Breaks on Second AJAX Call
in thread CGI Header Breaks on Second AJAX Call

I think you get the error message because you called exit() in your reduced example. Don't do that.

If you then still get the HTML with the HTTP headers in the HTML, then maybe try outputting the HTTP status code first:

print "200 OK\r\n"; print $q->header(-status => '200 OK', ...); ...

Apache looks for HTTP headers in the output of your script, and if it doesn't find them, it assumes that your script outputs raw HTML (which your browser then turns into more HTML). So if the above works, then maybe something else is outputting a string via print first, or you need to reconfigure Apache to (not?) want the HTTP status code first from your script.

Replies are listed 'Best First'.
Re^4: CGI Header Breaks on Second AJAX Call
by brandon8696 (Initiate) on Apr 15, 2025 at 21:00 UTC

    I wanted to get back to you and everyone here to finally say I solved this mystery.

    This is to date one of the most difficult things I've ever done as a programmer. I have learned a ton, but would quite frankly rather code vehicle physics for games, not debug core http functionality in Perl CGI haha.

    The darn jquery submit handler was nested incorrectly, and submitting the native form functionality and then the ajax submit form functionality. Somehow the two forms would work correctly upon submission, but I'm assuming form 1 would misconfigure the Apache header, so even though form 2 ran correctly, it was configured wrong upon return, thus sharting out a raw hash, even when I specified the headers.

    What made it even harder was the fact that it did NOT double print any statements even though it would double submit. So there was no "2FA hit" followed by another "2FA hit" in my debug logs. The logic in Perl only ran once. Conceptually, I still don't know how to describe exactly what happened, nor do I know how CGI Perl managed to kind of both gracefully handle it, and not handle it at the same time.

    I'm here to learn, so if anyone has any idea what behavior was happening between Apache and CGI Perl, I'd love a breakdown.