Re: MOD_PERL and OSX
On Thu, 11 Nov 2004, Mark S Lowe wrote: Thank you for your help! I added this module directive and still had the piping problem with output unless I use the CGI module, but since mod_perl perfers I do this, that is what I¹ll use. Thanks again! Wait, I'm confused -- did this or did this not fix the problem? You make it sound like it didn't work, but you're using it anyway (unless I'm just being thick, which is possible, as it's been a long day...). -- Chris Devers
Re: MOD_PERL and OSX
Is it okay if we keep this conversation on the list? On Thu, 11 Nov 2004, Mark S Lowe wrote: Ha! Well, I found that solution suggested on a site a couple weeks ago, and added it to my mod_perl httpd.conf. Still, the good old fashion Print ³content-type: text/html\n\n²; Print ³hello world\n²; Wouldn¹t work. So I have to use the CGI method of Header(³text/html²); $r-print(³hello world²); Having read a ton more about mod_perl, they suggest I use the latter to gain the best performance boost. I¹m guessing I can remove this TIE code and just follow the rules better. =) Ahh, I see. Weird, but if it works... -- Chris Devers
Re: MOD_PERL and OSX
My guess is that you have a version mismatch between mod_perl and perl. Ian On Nov 9, 2004, at 4:59 PM, Mark S Lowe wrote: It would seem after many attempts to get anything of any level of complexity running in mod_perl under OSX, that perhaps it cant be done. I have libraries that work fine in the normal cgi-bin, but constantly produce 500 server errors when running from my mod_perl mod-cgi bin. I can get little hello worlds running fine, but the second I try to access various built-in libraries, just the use statement cases fatal errors. Has anyone conquered the mod_perl world of OSX? Ive read every thread that has come through this forum for the last year. Those posts did help resolve the basics, but Im still left with a so so mod_perl engine. Any general direction or guidance would be great. Thanks. Mark
Re: MOD_PERL and OSX
On Tue, 9 Nov 2004, Mark S Lowe wrote: It would seem after many attempts to get anything of any level of complexity running in mod_perl under OSX, that perhaps it can¹t be done. I have libraries that work fine in the normal cgi-bin, but constantly produce 500 server errors when running from my mod_perl mod-cgi bin. I can get little hello worlds running fine, but the second I try to access various built-in libraries, just the ³use² statement cases fatal errors. Adding this line to your httpd.conf may help you: PerlHeaderParserHandler sub { tie *STDOUT, 'Apache' unless tied *STDOUT; } Details: http://devers.homeip.net:8080/blog/archives/64.html This seems to have fixed the problems I was having getting some mod_perl applications (Apache::MP3, etc) to work. -- Chris Devers