New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

150.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


HTTP XML/REST Value Sensor shows protocol violation. What can I do?

Votes:

0

Your Vote:

Up

Down

I'm trying to monitor an XML file via HTTP using the HTTP XML/REST Value sensor, but the sensor returns an error

The server committed a protocol violation. Section=ResponseStatusLine

What can I do?

error help http protocol prtg xml-rest

Created on Oct 21, 2011 12:13:01 PM by  Daniel Zobel [Paessler Support]

Last change on Nov 5, 2012 4:06:14 PM by  Daniel Zobel [Paessler Support]



3 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

The webserver's response is invalid. However, you can configure the sensor to use a more tolerant behavior. To do so, please create a new text file, containing

<?xml version="1.0"?>
<configuration>
<system.net>
    <settings>
        <httpWebRequest useUnsafeHeaderParsing="true" />
    </settings>
</system.net>
</configuration>

Save it as XMLValue.exe.config and copy it to the Sensor System sub-folder of your PRTG program directory.

Then the sensor should work as expected.

Created on Oct 21, 2011 12:16:57 PM by  Daniel Zobel [Paessler Support]

Last change on Oct 21, 2011 12:18:35 PM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

As of PRTG version 9.1.4.1839 (Nov 15th, 2011) this work around is not necessary any more.

Created on Nov 15, 2011 3:09:50 PM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Daniel,

We're on the latest version and are experiencing this issue. The workaround appears to not work either. When I load the page in a browser I get what looks like a valid XML file. It works fine on other XML applications but this is an internally developed service so is probably badly coded. Any other workarounds possible? (e.g. some way to get HTML advanced to just pick up words etc.)

<?xml version="1.0" encoding="UTF-8" ?>
<system1response>
    <action>ACTIONNAME</action>
    <response>SUCCESS</response>
    <responsedata xmlns:system1="http://schemas.system1.com/aci/">

etc.

Thanks, James

Created on May 2, 2012 4:19:53 PM by  jhsubscribe (50) 1 1

Last change on May 3, 2012 8:04:28 AM by  Daniel Zobel [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.