Hello Dan,
Thank you very much for your information.
Apparently this C::A::FastCGI "feature" affects me.
I would like to know how to overcome this
C::A::FastCGI bug without wrecking all my application code.

Could you please provide me any link or a sample of code which would show
how to use CGI::Application and FastCGI together, and
especially how to redirect url in cgiapp_prerun method.

Thanks again in advance.

Alex


Dan Horne wrote:
CGI User said:
Do you have any idea why redirect does work in
CGI::Application and it doesn't in CGI::Application::FastCGI
module?


Hi

It has been reported that there are issues with CGI::Application::FastCGI,
but I don't know if these affect you:

http://www.mail-archive.com/[email protected]/msg05359.html

I use CGI::Application and FastCGI without C::A::FastCGI, and make heavy
use of C::A::P::Redirect. If you have any questions on how to use them
together, I'll respond on this list

Dan


#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################



#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

Reply via email to