<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Parseresponse on Wapnet Blog</title><link>https://blog.wapnet.nl/tag/parseresponse/</link><description>Recent content in Parseresponse on Wapnet Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 18 Jul 2011 18:22:11 +0000</lastBuildDate><atom:link href="https://blog.wapnet.nl/tag/parseresponse/feed.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshoot (Nagios) Webinject</title><link>https://blog.wapnet.nl/2011/07/troubleshoot-nagios-webinject/</link><pubDate>Mon, 18 Jul 2011 18:22:11 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=591</guid><description>&lt;p&gt;There is a very nice GUI tool to troubeshoot webinject scripts. You can download the tool @ &lt;a href="http://www.webinject.org/download.html"&gt;http://www.webinject.org/download.html&lt;/a&gt; for Windows and Linux.&lt;/p&gt;
&lt;p&gt;After you extract or install the tool you can change the &lt;strong&gt;globalhttplog&lt;/strong&gt; line in the config.xml file to: &lt;strong&gt;&lt;globalhttplog&gt;yes&lt;/globalhttplog&gt;&lt;/strong&gt; so you get the full debug log.&lt;/p&gt;
&lt;p&gt;Note: I found a small memory bug in the GUI when you use the &lt;strong&gt;parseresponse&lt;/strong&gt; parameter in your scripts. To workaround this issue the best you can do is restart the tool (file &amp;gt; restart) before you test the scripts.&lt;/p&gt;</description></item></channel></rss>