in reply to Re: Using Mason with Mod_Perl 2 and getting "did not send an HTTP header" error
in thread Using Mason with Mod_Perl 2 and getting "did not send an HTTP header" error

I named it handshake3.html, I created many files for this. As long as the directive in httpd.conf matches the name of the file, I don't think it should really matter what the name is.
  • Comment on Re^2: Using Mason with Mod_Perl 2 and getting "did not send an HTTP header" error

Replies are listed 'Best First'.
Re^3: Using Mason with Mod_Perl 2 and getting "did not send an HTTP header" error
by Anonymous Monk on Mar 25, 2012 at 19:48 UTC

    I named it handshake3.html, I created many files for this. As long as the directive in httpd.conf matches the name of the file, I don't think it should really matter what the name is.

    And you have a seperate <Location section for each file? Eeeeew :D

      Yes, desperation often renders itself this way.
      Yes, I was desperate.