On Thu 24 Jan 2008, abhishek jain wrote: > > The server might not have mod_perl support and that's why it could make > > that error. > > Hi, i do not have access to error log as well, i am on a shared hosting,
I really doubt that a shared hoster that denies access to the error_log supports mod_perl. Even if so Embperl at least with mp2.x requires an extra LoadModule. To check if your server supports mod_perl at first I'd check the ServerTokens it sends with each reply: curl -I http://localhost HTTP/1.1 200 OK Date: Thu, 24 Jan 2008 08:07:34 GMT Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 OpenSSL/0.9.8e DAV/2 SVN/1.4.5 mod_apreq2-20051231/2.6.0 mod_perl/2.0.4-dev Perl/v5.8.8 You see my localhost supports mod_perl version 2.0.4-dev. If it reads only Server: Apache then the administrator has configured the minimal server tokens. That does not mean you don't have mod_perl. The next step would be a simple PerlResponseHandler something like that in your .htaccess (in case of mp2): PerlResponseHandler "sub { \ use Apache2::RequestRec; \ use Apache2::RequestIO; \ $_[0]->content_type( q{text/plain} ); \ $_[0]->print(qq{OK\\n}); \ return 0; \ }" All untested of course. Try it first on a local host where you are sure you have mod_perl and access to the error_log. If that works you have mod_perl2. But Embperl is another problem. Torsten --------------------------------------------------------------------- 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]
