Runtime Configuration

The behaviour of these functions is affected by settings in php.ini.

**SOAP Configure Options**
Name	Default	Changeable
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

Here's a short explanation of the configuration directives.

soap.wsdl_cache_enabled integer: 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 integer: Sets the number of seconds (time to live) that cached files will be used instead of the originals.
soap.wsdl_cache integer: 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 integer: 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

martijn at netexpo dot nl

3 years ago


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

7 years ago


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.]

no dot tehwan dot spam at com dot nospam dot gmail

1 year ago


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).