<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NetSVC  limitation in size of WebService's Reply]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I've jsut upgraded from 4.2 to 4.4, thus implicitly migrating from PortCheck to NetSVC.</p>
<p dir="auto">One of my HTTPS-WebService-Objects went into (and stayed in) status CRITICAL.<br />
Multiple other HTTPS-WebService-Objects are absolutely fine (status NORMAL), even the other one on the same Web-Server...</p>
<p dir="auto">...I think, it might be related to the Size of the actual Reply of queried WebService (446238 Bytes for the failed case).<br />
I created a nearly empty text-file "test.txt" on the Web-Server (with content "success") for the HTTPS-WebService-Object to query, which succeeded with the check and the status changed back to NORMAL.</p>
<p dir="auto">Is there such a limitations with NetSVC?</p>
<p dir="auto">Best regards,<br />
Manuel Schneider</p>
<p dir="auto">PS.: Please find an excerpt of nxagent-LOG with debug level 9 in the attachments, as well as the output of "curl --head" for the same WebService.</p>
<hr />
<p dir="auto"><a href="/assets/uploads/files/smf/0000000006498-nxagentd.txt">nxagentd.txt</a></p>
<p dir="auto"><a href="/assets/uploads/files/smf/0000000006499-curl.txt">curl.txt</a></p>
]]></description><link>https://forum.netxms.org/topic/7733/netsvc-limitation-in-size-of-webservice-s-reply</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:55:37 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7733.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 09 Aug 2023 12:54:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NetSVC  limitation in size of WebService's Reply on Fri, 11 Aug 2023 12:35:49 GMT]]></title><description><![CDATA[<p dir="auto">Yes, it was from the same host...<br />
...for my current workaround I just modified the Request-Portion in the Settings of the NetworkService-Object by appending the filename of the aforementioned txt-file:</p>
<p dir="auto">Doens't work: host.domain.tld:/<br />
Workaround: host.domain.tld:/test.txt</p>
]]></description><link>https://forum.netxms.org/post/32674</link><guid isPermaLink="true">https://forum.netxms.org/post/32674</guid><dc:creator><![CDATA[MSchneider]]></dc:creator><pubDate>Fri, 11 Aug 2023 12:35:49 GMT</pubDate></item><item><title><![CDATA[Reply to NetSVC  limitation in size of WebService's Reply on Fri, 11 Aug 2023 12:30:22 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">There should not be length limitation, I've just tried 500000 byte log web page and it works fine.</p>
<p dir="auto">Possible reason could be that libcurl, on which NetSVC is based is checking tls certificates. The curl output that you provided - was that curl executed on the same system where netxms agent is running?</p>
]]></description><link>https://forum.netxms.org/post/32673</link><guid isPermaLink="true">https://forum.netxms.org/post/32673</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Fri, 11 Aug 2023 12:30:22 GMT</pubDate></item></channel></rss>