[PHP-BUG] Bug #63271 [NEW]: SOAP wsdl cache is not enabled after initial requests
From: jawed Operating system: Any PHP version: 5.4Git-2012-10-13 (Git) Package: SOAP related Bug Type: Bug Bug description:SOAP wsdl cache is not enabled after initial requests Description: SOAP wsdl cache is not enabled after initial requests because the OnUpdateCacheEnabled is not always called per request context. Because of this, SOAP_GLOBAL(cache) is almost always "0" and WSDL caching is disabled. WSDL caching is enabled and the caching type is set to WSDL_CACHE_MEMORY (although the cache type doesn't matter). Expected result: On subsequent requests after MINIT ext/soap returns the persistent sdlPtr. Actual result: -- On subsequent requests after MINIT ext/soap does not return the persistent sdlPtr because SOAP_GLOBAL(cache) is 0 (even though the sdlPtr exists in SOAP_GLOBAL(mem_cache)). -- Edit bug report at https://bugs.php.net/bug.php?id=63271&edit=1 -- Try a snapshot (PHP 5.4): https://bugs.php.net/fix.php?id=63271&r=trysnapshot54 Try a snapshot (PHP 5.3): https://bugs.php.net/fix.php?id=63271&r=trysnapshot53 Try a snapshot (trunk): https://bugs.php.net/fix.php?id=63271&r=trysnapshottrunk Fixed in SVN: https://bugs.php.net/fix.php?id=63271&r=fixed Fixed in release: https://bugs.php.net/fix.php?id=63271&r=alreadyfixed Need backtrace: https://bugs.php.net/fix.php?id=63271&r=needtrace Need Reproduce Script: https://bugs.php.net/fix.php?id=63271&r=needscript Try newer version: https://bugs.php.net/fix.php?id=63271&r=oldversion Not developer issue:https://bugs.php.net/fix.php?id=63271&r=support Expected behavior: https://bugs.php.net/fix.php?id=63271&r=notwrong Not enough info: https://bugs.php.net/fix.php?id=63271&r=notenoughinfo Submitted twice: https://bugs.php.net/fix.php?id=63271&r=submittedtwice register_globals: https://bugs.php.net/fix.php?id=63271&r=globals PHP 4 support discontinued: https://bugs.php.net/fix.php?id=63271&r=php4 Daylight Savings: https://bugs.php.net/fix.php?id=63271&r=dst IIS Stability: https://bugs.php.net/fix.php?id=63271&r=isapi Install GNU Sed:https://bugs.php.net/fix.php?id=63271&r=gnused Floating point limitations: https://bugs.php.net/fix.php?id=63271&r=float No Zend Extensions: https://bugs.php.net/fix.php?id=63271&r=nozend MySQL Configuration Error: https://bugs.php.net/fix.php?id=63271&r=mysqlcfg
Bug #63271 [PATCH]: SOAP wsdl cache is not enabled after initial requests
Edit report at https://bugs.php.net/bug.php?id=63271&edit=1 ID: 63271 Patch added by: ja...@php.net Reported by: ja...@php.net Summary:SOAP wsdl cache is not enabled after initial requests Status: Open Type: Bug Package:SOAP related Operating System: Any PHP Version:5.4Git-2012-10-13 (Git) Block user comment: N Private report: N New Comment: The following patch has been added/updated: Patch Name: 0001-Fix-SOAP-wsdl-cache-failing-to-look-at-mem_cache.patch Revision: 1350107221 URL: https://bugs.php.net/patch-display.php?bug=63271&patch=0001-Fix-SOAP-wsdl-cache-failing-to-look-at-mem_cache.patch&revision=1350107221 Previous Comments: [2012-10-13 05:46:41] ja...@php.net Description: SOAP wsdl cache is not enabled after initial requests because the OnUpdateCacheEnabled is not always called per request context. Because of this, SOAP_GLOBAL(cache) is almost always "0" and WSDL caching is disabled. WSDL caching is enabled and the caching type is set to WSDL_CACHE_MEMORY (although the cache type doesn't matter). Expected result: On subsequent requests after MINIT ext/soap returns the persistent sdlPtr. Actual result: -- On subsequent requests after MINIT ext/soap does not return the persistent sdlPtr because SOAP_GLOBAL(cache) is 0 (even though the sdlPtr exists in SOAP_GLOBAL(mem_cache)). -- Edit this bug report at https://bugs.php.net/bug.php?id=63271&edit=1
Bug #63271 [Com]: SOAP wsdl cache is not enabled after initial requests
Edit report at https://bugs.php.net/bug.php?id=63271&edit=1 ID: 63271 Comment by: ja...@php.net Reported by: ja...@php.net Summary:SOAP wsdl cache is not enabled after initial requests Status: Open Type: Bug Package:SOAP related Operating System: Any PHP Version:5.4Git-2012-10-13 (Git) Block user comment: N Private report: N New Comment: Pull request: https://github.com/php/php-src/pull/215 Previous Comments: [2012-10-13 05:47:01] ja...@php.net The following patch has been added/updated: Patch Name: 0001-Fix-SOAP-wsdl-cache-failing-to-look-at-mem_cache.patch Revision: 1350107221 URL: https://bugs.php.net/patch-display.php?bug=63271&patch=0001-Fix-SOAP-wsdl-cache-failing-to-look-at-mem_cache.patch&revision=1350107221 [2012-10-13 05:46:41] ja...@php.net Description: SOAP wsdl cache is not enabled after initial requests because the OnUpdateCacheEnabled is not always called per request context. Because of this, SOAP_GLOBAL(cache) is almost always "0" and WSDL caching is disabled. WSDL caching is enabled and the caching type is set to WSDL_CACHE_MEMORY (although the cache type doesn't matter). Expected result: On subsequent requests after MINIT ext/soap returns the persistent sdlPtr. Actual result: -- On subsequent requests after MINIT ext/soap does not return the persistent sdlPtr because SOAP_GLOBAL(cache) is 0 (even though the sdlPtr exists in SOAP_GLOBAL(mem_cache)). -- Edit this bug report at https://bugs.php.net/bug.php?id=63271&edit=1
Bug #63363 [Com]: Curl silently accepts boolean true for SSL_VERIFYHOST
Edit report at https://bugs.php.net/bug.php?id=63363&edit=1 ID: 63363 Comment by: ja...@php.net Reported by:ircmax...@php.net Summary:Curl silently accepts boolean true for SSL_VERIFYHOST Status: Assigned Type: Bug Package:*Network Functions Operating System: All PHP Version:Irrelevant Assigned To:ircmaxell Block user comment: N Private report: N New Comment: Thx for creating the bug. Here is the pull request against master: https://github.com/php/php-src/pull/221 The change is minimal and the difference between ext/curl/interface.c from master to >5.4 is also minimal. This should be easy to cherry-pick from master. - JJ Previous Comments: [2012-10-25 16:41:21] ircmax...@php.net Description: The CURL option SSL_VERIFYHOST accepts a long value to indicate the verification that should be applied. The following values are valid: 0 - No verification 1 - Check a host is present in cert 2 - Check cert's host matches request's host The problem is that a boolean true is cast to a long 1. Therefore, code that does the following: curl_setopt($c, CURLOPT_SSL_VERIFYHOST, true) appears to be verifying the host. However, it's actually not. This can create security issues that are very hard to find by reading code. Test script: --- https://bugs.php.net/bug.php?id=63363&edit=1
