Phpinfo is used in the visualamp integration environment. for php detection, ServerAPI displays CGIFastCGI, for example, without detailed information under apache2handler. For example, there is a loadedmodules in these figures that shows the loaded modules, do Not Display these loaded modules, that is...
The visual amp integration environment uses Phpinfo. php for detection. The Server API displays CGI/FastCGI, for example,
Details under apache2handler are not displayed, as shown in,
In these figures, there is a loaded modules that shows the loaded modules, not the loaded modules, that is, the modules related to apache that have not been loaded successfully.
Other integration environments, such as wamp appserv, are detected using phpinfo. php. The Server API displays Apache 2.0 Handler, such
That is, the related modules of apache have been loaded successfully.
It is found that the Server API in Phpinfo. php can normally display Apache 2.0 Handler, which is in the apache configuration file.
There is such a LoadModule php5_module in httpd. conf "../php/php5apache2_4.dll"
There are two versions of php5: None Thread Safe (CNT, non-Thread security) and Thread Safe (TS, Thread security ),
The php version of the brigade does not contain the php5apache2_4.dll file, that is, the module cannot be loaded using the load module,
The other is TS, which contains the php5apache2_4.dll file. In principle, you can use the load module to load the module,
Return to the visual amp integration environment, load the file with the load module in its apache httpd. conf, and restart
Apache and Server APIs still display CGI/FastCGI, so there is no detailed information under apache2handler, as shown in
. That is, apache cannot load many modules.
I don't know how to make the visual amp display the loaded module information (many modules have been configured and loaded .)
Reply content:
The visual amp integration environment uses Phpinfo. php for detection. The Server API displays CGI/FastCGI, for example,
Details under apache2handler are not displayed, as shown in,
In these figures, there is a loaded modules that shows the loaded modules, not the loaded modules, that is, the modules related to apache that have not been loaded successfully.
Other integration environments, such as wamp appserv, are detected using phpinfo. php. The Server API displays Apache 2.0 Handler, such
That is, the related modules of apache have been loaded successfully.
It is found that the Server API in Phpinfo. php can normally display Apache 2.0 Handler, which is in the apache configuration file.
There is such a LoadModule php5_module in httpd. conf "../php/php5apache2_4.dll"
There are two versions of php5: None Thread Safe (CNT, non-Thread security) and Thread Safe (TS, Thread security ),
The php version of the brigade does not contain the php5apache2_4.dll file, that is, the module cannot be loaded using the load module,
The other is TS, which contains the php5apache2_4.dll file. In principle, you can use the load module to load the module,
Return to the visual amp integration environment, load the file with the load module in its apache httpd. conf, and restart
Apache and Server APIs still display CGI/FastCGI, so there is no detailed information under apache2handler, as shown in
. That is, apache cannot load many modules.
I don't know how to make the visual amp display the loaded module information (many modules have been configured and loaded .)