logical fix for unexpected parsing results
authorgggeek <giunta.gaetano@gmail.com>
Sat, 25 Feb 2023 13:28:59 +0000 (13:28 +0000)
committergggeek <giunta.gaetano@gmail.com>
Sat, 25 Feb 2023 13:28:59 +0000 (13:28 +0000)
src/Request.php

index 0b89150..203113e 100644 (file)
@@ -357,7 +357,7 @@ class Request
         }
         // third error check: parsing of the response has somehow gone boink.
         /// @todo shall we omit this check, since we trust the parsing code?
-        elseif ($_xh['isf'] > 3 || $returnType == XMLParser::RETURN_XMLRPCVALS && !is_object($_xh['value'])) {
+        elseif ($_xh['isf'] > 3 || ($returnType == XMLParser::RETURN_XMLRPCVALS && !is_object($_xh['value']))) {
             // something odd has happened and it's time to generate a client side error indicating something odd went on
             $r = new Response(0, PhpXmlRpc::$xmlrpcerr['xml_parsing_error'], PhpXmlRpc::$xmlrpcstr['xml_parsing_error'],
                 '', $httpResponse