php extension path confusion under apache (xp)

What conf/paths/envs do I need to set to get the php_openssl.dll
extension loading properly under Apache/winxp?

>From the command the line this dll loads and operates fine (static
php.ini or dynamic loading) but under apache it reports the dll "not
found" (twice) on startup. In desperation I tried copying the extension
dll (and another one it depends on) into winnt/system32 - but no
difference.

(Failing a solution any other handy route to https?)

tx.

otto wrote:
> What conf/paths/envs do I need to set to get the php_openssl.dll
> extension loading properly under Apache/winxp?
>
>>From the command the line this dll loads and operates fine (static
> php.ini or dynamic loading) but under apache it reports the dll "not
> found" (twice) on startup. In desperation I tried copying the extension
> dll (and another one it depends on) into winnt/system32 - but no
> difference.
>
> (Failing a solution any other handy route to https?)
>
> tx.
>
Did you set the PHPIniDir entry in your httpd file?
You need to have a LoadModule and PHPIniDir entry.

-david-

David Haynes wrote:
> otto wrote:
> > What conf/paths/envs do I need to set to get the php_openssl.dll
> > extension loading properly under Apache/winxp?
> >
> Did you set the PHPIniDir entry in your httpd file?
> You need to have a LoadModule and PHPIniDir entry.
>
Yup:-

# httpd.conf
PHPIniDir "c:/php/5.0.5"
LoadModule php5_module "c:/php/5.0.5/php5apache2.dll"

I should perhaps add that the gd2 and mysql extensions are in the same
place and load just fine. So there must be some "extra" issue with
opensll. I understand it uses libeay32.dll - this dll is in the same
directory as opensll.dll (and the other two extensions that work all
the time). And as mentioned previously it all works fine from the
command line.

(migrating thread to php.install)

otto wrote:
> David Haynes wrote:
> > otto wrote:
> > > What conf/paths/envs do I need to set to get the php_openssl.dll
> > > extension loading properly under Apache/winxp?
> > >
> > Did you set the PHPIniDir entry in your httpd file?
> > You need to have a LoadModule and PHPIniDir entry.
> >
> Yup:-
>
> # httpd.conf
> PHPIniDir "c:/php/5.0.5"
> LoadModule php5_module "c:/php/5.0.5/php5apache2.dll"
>
> I should perhaps add that the gd2 and mysql extensions are in the same
> place and load just fine. So there must be some "extra" issue with
> opensll. I understand it uses libeay32.dll - this dll is in the same
> directory as opensll.dll (and the other two extensions that work all
> the time). And as mentioned previously it all works fine from the
> command line.

Bingo! Thought I would share this as it appears many may be caught out
by this...

(php 5.0.5, apache2, winXP)

*** The php directory must be in the env path of the Apache2 service
(e.g. in the system path) or else some php extensions will mysteriously
fail to load ***

In my case the php extension dlls are in the php root. If yours are
elsewhere you may need that on the system path instead (or as well?).

Note: You must restart the entire Apache2 service (or reboot) for the
new system path to take effect - it is not sufficient to restart the
Apache instance using the tray tool.

I am guessing that "extension_dir" isnt being used when looking for
pre-requistive dlls - don't have time to investigate just now.

p.s. I also noticed that "restarting" Apache2 from the tray tool
doesn't reload the php extension dlls already installed - you must
"stop" then "start" if you want to be sure you've got the right dll
versions on board!*!

> otto wrote:
> > David Haynes wrote:
> > > otto wrote:
> > > > What conf/paths/envs do I need to set to get the php_openssl.dll
> > > > extension loading properly under Apache/winxp?
> > > >
> > > Did you set the PHPIniDir entry in your httpd file?
> > > You need to have a LoadModule and PHPIniDir entry.
> > >
> > Yup:-
> >
> > # httpd.conf
> > PHPIniDir "c:/php/5.0.5"
> > LoadModule php5_module "c:/php/5.0.5/php5apache2.dll"
> >
> > I should perhaps add that the gd2 and mysql extensions are in the same
> > place and load just fine. So there must be some "extra" issue with
> > opensll. I understand it uses libeay32.dll - this dll is in the same
> > directory as opensll.dll (and the other two extensions that work all
> > the time). And as mentioned previously it all works fine from the
> > command line.