Forum OpenACS Development: Re: XML-RPC String limit

Collapse
7: Re: XML-RPC String limit (response to 6)
Posted by Iuri Sampaio on
I downloaded and replaced the TCL file https://github.com/openacs/xml-rpc/blob/master/tcl/xml-rpc-procs.tcl. Curiously, my file was different than that one.

I've pasted the results in the previous post. There's no errors within that JS code. Plus, I've removed that chunk of code and the log notice threw another chunk from the same TCL in a different part of the file. It seems that the chunk gets returned in the error.log as a side effect of the parsing execution.

-] Error: xmlrpc::invoke: error parsing request: error "Unexpected end" at position 0
""
[14/Apr/2017:02:32:06][1460.7ff7f68ea700][-conn:1contact:1-] Notice: error "Entity parsing error" at position 1903
" + '?locale='+l+'&return_url='+return_url;
top.location.href=url;
}
--Error-- /script
script type="text/javascript" src="https://code.jquery.com/jquery-";
[14/Apr/2017:02:32:06][1460.7ff7f70eb700][-conn:1contact:0-] Notice: checking entry 127.0.0.1 from host_node_map

Collapse
8: Re: XML-RPC String limit (response to 7)
Posted by Gustaf Neumann on
what is the result of the "nslog notice ..." statement of
https://openacs.org/forums/message-view?message_id=5358474 ?
Collapse
9: Re: XML-RPC String limit (response to 8)
Posted by Iuri Sampaio on
To knock your suspects off see bellow the xml request file of a successful attempt. Then, make X times "100000, to get a body with 100000 X's char and break xmlrpc.

#####
Chrome/40.0.2214.111 Safari/537.36 user_id 698 peer 127.0.0.1
[14/Apr/2017:17:11:58][3231.7fef5a8db700][-conn:1contact:0-] Notice: Running TCL script test_ws.tcl
[14/Apr/2017:17:11:58][3231.7fef5a8db700][-conn:1contact:0-] Warning: ns_httpopen POST http://1c.1contact.ch/RPC2/ d4 30 {?xml version="1.0"?<methodCall><methodName>ix_robot.parseJson</methodName><params><param><value><string>gtregivrwjvoiejviowvwgvwegvwgre</string></value></param><param><value><string>XXXXXXXXX</string></value></param></params></methodCall>} is deprecated. Use 'ns_http' instead!
[14/Apr/2017:17:11:58][3231.7fef5a0da700][-conn:1contact:1-] Notice: Running ad_proc ix_robot.parseJson ...
[14/Apr/2017:17:11:58][3231.7fef5a0da700][-conn:1contact:1-] Notice: gtregivrwjvoiejviowvwgvwegvwgre
[14/Apr/2017:17:11:58][3231.7fef5a0da700][-conn:1contact:1-] Notice: JSON
XXXXXXXXX
[14/Apr/2017:17:11:58][3231.7fef5a8db700][-conn:1contact:0-] Notice:
[14/Apr/2017:17:12:00][3231.7fef5a0da700][-conn:1contact:1-] Notice: CSP violation: {"csp-report":{"document-uri":"http://1c.1contact.ch/","referrer":"","violated-directive":"font-src 'self' data:","effective-directive":"font-src","original-policy"

Furthemore, see the results of ns_log Debug

####
ted. Use 'ns_http' instead!
[14/Apr/2017:17:16:16][3231.7fef5a0da700][-conn:1contact:1-] Notice: BEFORE DEBUG
[14/Apr/2017:17:16:16][3231.7fef5a0da700][-conn:1contact:1-] Error: xmlrpc::invoke: error parsing request: error "Unexpected end" at position 0
####

And the collateral effect of XML RPC parsing

######
[14/Apr/2017:17:16:16][3231.7fef5a8db700][-conn:1contact:0-] Notice: error "Entity parsing error" at position 2006
" + '?locale='+l+'&return_url='+return_url;
top.location.href=url;
}
--Error-- /script
script type="text/javascript" src="https://code.jquery.com/jquery-";
[14/Apr/2017:17:16:16][3231.7fef5a0da700][-conn:1contact:1-] Error: can't read "doc": no such variable
while executing
"xml_doc_free $doc"
(procedure "xmlrpc::invoke" line 39)
invoked from within
"xmlrpc::invoke $content"
("uplevel" body line 15)