I faced this problem as well and here's what I ended up doing:

sub irregular_run_mode {
  my $app = shift;
  $app->header_type("none");
  $| = 1;

  print $app->query()->header();


  # code here

  return "";
}
[download]

Yeah. It tends not to work too well if you use cgiapp_postrun to alter the output. Of course, you can fix that with:

sub cgiapp_postrun {
  my ($app,$outref) = @_;
  return $outref if $app->get_current_runmode() eq "irregular_run_mode
+";

  # ...
}
[download]

Note: I consider this to a be a hack and rather ugly. Please leave comments so if someone wishes to alter the irregular_run_mode so it works normally they will know that they need to alter cgiapp_postrun as well.

I too face this problem, and tried your hack above.

It works as long as I don't have to use the Authentication plugin. With Authentication plugin, it seems that any irregular mode that is protected by the plugin can never be displayed. Whenever you try to go to that mode, you get the login box, and even if you enter the right credentials, you get to the login box again.

I haven't quite figured out why yet, but I think it's because session state is transmitted by cookies, which themselves are transmitted through http headers. And the specific cookie headers generated by Authentication plugin are not available until AFTER the body has been generatied (the cookie headers are being generated by a postrun hook for some strange reason). In a standard runmode that doesn't matter, because the headers are prepended to the body before the whole thing is outputted. But with an irregular mode, you need to generate and print the headers before you generate and print the body.

Has anybody solved this problem?

Post some code :) ( How do I post a question effectively? and all that )

Also, even though jfroebe and antirice have visited this year, see also on necromancy (reviving old threads)

You can flush output by closing STDOUT as soon as you've printed everything you mean to. The client then thinks the script is done, and you're free to continue processing.

Added: Hmm, take that as a general statement - it doesn't seem to fit in with the CGIA way.

Just for other people's notes, the CGI::Application way would be to return the page's text or a reference to it at the end of your script and then C'A takes care of the task of sending the http headers and page to the browser. You are normally expected to not print.

Yup, I've pretty much decided to write a short disclaimer: may take a little while or similar.

Thanks everyone!

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1