This might be a bit of a foolish question, however after reading the documentation of the "http transaction" sensor, I was led to believe that setting the sensor to "get" requests the webpage directly, just as you and I would browse to it. What I find puzziling is that this sensor has completley different data to the "full web page" sensor set to the same website
Http transaction on "get" will give around 4 seconds
Http "full web page" will give around 10 seconds
What is different about the sensors?
Article Comments
Only the Full Page sensor actually loads all the embedded objects (images, scripts, JAVA applets, etc.) - all other HTTP sensors only load the HTML source code directly from the document under the specified URL. Beyond that, all other HTTP sensors do not execute active elements (e.g. Javascript) in the HTML code. This can also make a difference if, for example, code is loaded after the initial connection.
Jan, 2013 - Permalink
Thanks, that is exactly what I was after :)
Jan, 2013 - Permalink
Only the Full Page sensor actually loads all the embedded objects (images, scripts, JAVA applets, etc.) - all other HTTP sensors only load the HTML source code directly from the document under the specified URL. Beyond that, all other HTTP sensors do not execute active elements (e.g. Javascript) in the HTML code. This can also make a difference if, for example, code is loaded after the initial connection.
Jan, 2013 - Permalink