Open gh0stwizard opened 5 years ago
When open the body of a huge message via XML-RPC on another host you may get XML error No memory.
No memory
View content of the message like always.
Error: Invalid return payload: enable debugging to examine incoming payload (XML error: No memory at line 8, column 18)
HEADER: date: Fri, 12 Jul 2019 15:59:53 GMT HEADER: server: Apache HEADER: x-powered-by: PHP/7.2.19 HEADER: x-xss-protection: 1; mode=block HEADER: x-frame-options: SAMEORIGIN HEADER: x-content-type-options: nosniff HEADER: set-cookie: PHPSESSID=XXXXXXXXXXXXXXXXXXXXXXX; path=/; HttpOnly HEADER: expires: Thu, 19 Nov 1981 08:52:00 GMT HEADER: cache-control: no-store, no-cache, must-revalidate HEADER: pragma: no-cache HEADER: vary: Accept-Encoding HEADER: content-encoding: gzip HEADER: content-length: 9898790 HEADER: content-type: text/xml;charset=UTF-8 COOKIE: PHPSESSID=XXXXXXXXXXXXXXXXXXXXXXX XML error: No memory at line 8, column 18Error: (error06) Invalid return payload: enable debugging to examine incoming payload (XML error: No memory at line 8, column 18)
Revisiting this....XML-RPC has no viable workarounds without custom coding of the library, going to explore implementing a RESTful API instead....
Issue summary
When open the body of a huge message via XML-RPC on another host you may get XML error
No memory
.Steps to reproduce
Expected result
View content of the message like always.
Actual result
Error: Invalid return payload: enable debugging to examine incoming payload (XML error: No memory at line 8, column 18)
Installation
Version and method
Server configuration
Client configuration
References about the issue