Thanks a lot for your advice. The file shows the html result so I guess there has been some changes between Apache 2.0.46 and 2.2.3 that prevents the 2.2.3 to understand the html headers on the page... I will look in that direction Thanks again Denis
"Octavian Rasnita" <[EMAIL PROTECTED]> To <[email protected]> cc Subject Re: [EMAIL PROTECTED] problem with perl script and Apache "Octavian Rasnita" <[EMAIL PROTECTED]> Please respond to : [email protected] 30/05/2008 15:49 How does it look the content of the downloaded perl file? It shows the perl source code, or the html page which should be created by the script? If it shows the source code, it means that the program is not executed because Apache is not configured correctly. If it shows the html result, it means that the script doesn't send the correct HTTP headers, so you should fix the script. Octavian ----- Original Message ----- From: "Denis Peuziat" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, May 30, 2008 3:18 PM Subject: [EMAIL PROTECTED] problem with perl script and Apache > Apache 2.2.3 + Perl 5.8.8 on SUSE SLES10 > > I have just migrated a site from a linux RH server with Apache 2.0.46 and > perl 5.8.0 to a server with the config above. > > Some perls scripts that are still executing correctly on the old server, > are now identified as Unknown files when page is launched in a webbrowser > (pop up asking to open or save document) > > I say some because other pages containing perl scripts are working as > expected..... > > The same scripts are working when executed locally on the server with perl > xxxx.pl command. > > The only difference is that these scripts are using a "home-developed" > module. > > Would it be possible that the change of environment would render the > module useless? > > Thanks for your help > > Denis --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
