运行时配置

这些函数的行为受 php.ini 中的设置影响。

**SOAP 配置选项**
名字	默认	可修改范围
soap.wsdl_cache_enabled	1	PHP_INI_ALL
soap.wsdl_cache_dir	/tmp	PHP_INI_ALL
soap.wsdl_cache_ttl	86400	PHP_INI_ALL
soap.wsdl_cache	1	PHP_INI_ALL
soap.wsdl_cache_limit	5	PHP_INI_ALL

这是配置指令的简短说明。

soap.wsdl_cache_enabled int: Enables or disables the WSDL caching feature.
soap.wsdl_cache_dir string: Sets the directory name where the SOAP extension will put cache files.
soap.wsdl_cache_ttl int: Sets the number of seconds (time to live) that cached files will be used instead of the originals.
soap.wsdl_cache int: If soap.wsdl_cache_enabled is on, this setting determines the type of caching. It can be any of: WSDL_CACHE_NONE (0), WSDL_CACHE_DISK (1), WSDL_CACHE_MEMORY (2) or WSDL_CACHE_BOTH (3). This can also be set via the options array in the SoapClient or SoapServer constructor.
soap.wsdl_cache_limit int: Maximum number of in-memory cached WSDL files. Adding further files into a full memory cache will delete the oldest files from it.

User Contributed Notes

michal-ok at o2 dot pl 06-Mar-2020 03:08


Be aware that wsdl cache may not be compatible across different PHP versions, which may be important to know when you upgrade your PHP on the same system or use a multi-PHP version setup where you run the same scripts from different PHP versions. In other words, when a SOAP request writes a file to the cache and then you make another SOAP request from another PHP version and this cache file is used then *sometimes* you may experience unexpected errors that you will not know where they come from.



I spent hours trying to figure out why I was getting "Encoding: Violation of encoding rules" errors every time I ran some of my SOAP scripts from PHP 7.3 just hours after switching from PHP 7.2. It turned out I needed to clear all cached wsdl files created by PHP 7.2. Downgrading from 7.3 to 7.2 caused the same errors and required clearing the cache, too.



When transitioning to a new PHP version you may turn off the cache or set a very short wsdl_cache_ttl period - if you can't delete the files yourself. If you need your scripts to run on multiple PHP versions with wsdl cache then you'd need to set wsdl_cache_dir that is different for each PHP version.

no dot tehwan dot spam at com dot nospam dot gmail 20-Aug-2014 08:05


Keep in mind if you have memory cache enabled that even if you use an updated WSDL file, it will still be using the one in memory. If you download the WSDL files yourself, avoid using memory cache as you will have no control over it, or set the TTL to a small value (default is 1 day).

martijn at netexpo dot nl 19-Oct-2012 01:37


Please note that these three ini settings will also affect the behaviour of your soap server (and clients as well) :



1. default_socket_timeout default 60 secs

Large or slow requests to your soap server or long processes at your soap server will return soap fault after 60 secs like : Error Fetching http headers.



2. max_execution_time default 30 secs

This can be the next bottleneck (but only when your default_socket_timeout is larger then this setting). Your soap server will not return anything, no faults no output, just an empty string.



3. memory_limit default 128M

Will throw fatal errors when the soap server script itself has low memory or will let your services return empty strings when the data it processes puts memory usage over this limit.



Other max POST settings luckily (but a bit suprisingly to me) have _no_ effect for your soap server. Those are : 



max_input_time

max_input_nesting_level

max_input_vars

post_max_size

suhosin.post.max_array_depth

suhosin.post.max_array_index_length

suhosin.post.max_name_length

suhosin.post.max_totalname_length

suhosin.post.max_vars

suhosin.post.max_value_length

hpralow at users dot sf dot net 24-Jul-2008 07:40


If you want to dissable WSDL-caching, you can do so with 


<?php


ini_set('soap.wsdl_cache_enabled', '0');


ini_set('soap.wsdl_cache_ttl', '0');


?>


However you must do this before creating a SOAP object (soap_client or soap_server). 


Changing the settings like above does not have any effect on already existing soap-objects.





[EDIT BY danbrown AT php DOT net: Typofix provided by (james AT voodoo DOT co DOT uk) on 4-FEB-09.]