php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #57644 SCA_Bindings_XXX_RequestTester::isServiceRequest()
Submitted: 2007-05-03 09:19 UTC Modified: 2017-01-10 08:06 UTC
From: michael dot caplan at henryschein dot com Assigned:
Status: Suspended Package: SCA_SDO (PECL)
PHP Version: 5.2.1 OS: CentOS 4
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: michael dot caplan at henryschein dot com
New email:
PHP Version: OS:

 

 [2007-05-03 09:19 UTC] michael dot caplan at henryschein dot com 
Description:
------------
I have a server that uses both the SOAP and XMLRPC bindings (defined in that order in the class docblock annotation).  When trying to do XMLRPC introspection, it fails because the server detects the request as SOAP, and returns a SOAP payload. It appears that the detection logic in SCA_Bindings_soap_RequestTester::isServiceRequest() overlaps with what an XMLRPC "fingerprint" looks like.

If I swap the bindings, so that XMLRPC is evaluated first, SCA_Bindings_Xmlrpc_RequestTester::isServiceRequest() will be properly detected.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-05-03 11:56 UTC] mfp@php.net 
Yes, you are right. The tests overlap as both xmlrpc and soap respond to content-type=text/xml. And we need to tighten up the tests so they don't overlap.

Trouble is to tighten the tests we will probably have to examine the payload, and not just the headers. That means taking a look at the XML. Any suggestions for exactly what the best things to test for gratefully received.

Your only option at the moment is to order the @bindings, as you have done. 

I accept this one.
 [2007-05-03 11:59 UTC] michael dot caplan at henryschein dot com 
humm, would it be helpful to segment all different service binding out into some sort of URL namespace?  For example, for XMLRPC, it looks for PATH_INFO /RPC2.  If we extended this convension to all binding, it could make detection much easier.

What do you think?
 [2017-01-10 08:06 UTC] kalle@php.net
-Status: Assigned +Status: Suspended -Assigned To: mfp +Assigned To:
 [2017-01-10 08:06 UTC] kalle@php.net 
Suspending this report as the extension have not had a release for almost 9 years.  Please revive this if the extension once again shows life
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Oct 31 23:01:28 2024 UTC