HTTP methods
HTTP methods HTTP methods define actions, wished to perform to a specific site.

GET method is used when the page is loaded from server to your browser. If it works, your web page is available to load. It is the most common method among all, when you type a site address in your broswer - this method is used to show you the site content.

HEAD method is similar with GET, but it load from server only headers of your page. It is useful if You want to test just accessibility of a web page or review its headers.

POST method is used to send information from you to server. If a page includes text field(s) for filling, POST method is used when you click button "submit" (or whatever is name of that button). It brings information you have typed into those fields to server. So, if there are some text fields on your page, you can use this method. If it works, your web page is available to use, and text, typed into fields on your page, is able to be transferred to the server. An example of using POST method for Website Monitoring is provided in this article (You provide specific keywords, which are inserted into text fields).

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.HTTP
  • CM.Glossary.POSTMethodExample
more glossary
"

Keep up the good work!

"
- biz
Shellshock vulnerability online check

Considering the recently discovered Shellshock vulnerability, HostTracker has created a tool for testing it.

Check your server for vulnerability

How does it work?

It is developed for a Linux server with a web server installed on it. The algorithm is very simple. We consequently generate 4 http requests:

  • 1. Ordinary request
  • 2. The request tries, using vulneratility, post a "harmful" cookie which causes 2-seconds delay in respond to our special http request.
  • 3. The request tries, using vulneratility, post a "harmful" cookie which causes 4-seconds delay in respond to our special http request.
  • 4. Same as #3

How to understand the result?

We compare response time for all 4 requests. Three situation are possible:

  • 1. Vulnerability found. We may affirm that if the difference in responses is about 2 seconds for requests without cookie and with 2-second-delay cookie, as well as for requests with 2 and 4-second delay cookie. It means that our request was able to use the vulnerability and set these cookies.
  • 2. Vulnerability not found. All the requests have about the same response time. The cookies, likely, were not installed because there is no vulnerability.
  • 3. Uncertain situation. If the response time differs widely, without coincidence with preset by cookies delay, we can not say for sure. It could be if the server is under high load. To check this, we use two requests with same cookies (#3 and #4). If the response time for two same checks varies, we make a conclusion that the response time is not affected by cookies. At least, not only by them. So in this case our method can not detect vulnerability

Safety of checks

Our test can not damage your server. The risk consists of appearance of one extra-cookie, which is used only for our requests and can not affect normal work-flow of your site.

more blog
Thank you for feedback!
 
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Glossary > ContentCheck
Content CheckContent check is a way to check the presence of specific info on the page.
Content Check Content check is a way to check the presence of specific info on the page.

Content check is a way to check the presence/absence of specific info on the page. It helps to check not just the page itself for accessibility, but the performance of the site too. It is useful for sites with complicated structure - which contain many scripts and data that is stored in database or other off-site storages. In this case, there is possible cases when the page itself is working fine while some of the linked resources are not available - thus, some info on the page is missed.

HostTracker provides tools to solve this problem. You may create ContentCheck task and provide specific keywords for monitoring:

There are several important things on that screen:

Content Check - set of comma-separated keywords to look for.
Advanced Content Check option - useful for immediate detection of the reasons of a problem. In case of appearance of the keyword, the phrase, previous to the keyword, is sent you as the result of the check. For example, you enter keyword exception and select this option. Somehow, on the page appears the statement: Wrong SQL statement on the line 123 exception. In this case, you get an alert saying Wrong SQL statement on the line 123.
Conditions Field - allows to specify conditions for set of keywords. You may set to detect an error in case of presence/absence of all entered keywords, or just any of them.

For monitoring the presence of images, videos, execution scripts - you may choose a keyword from their description, or add a special short script which will return Error or other keyword if something is missed.

Restrictions:
Only first 10 Kb of page are analysed
Only first 120 characters of each line are analysed

  • CM.Glossary.Uptime
  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Uptime
  • CM.Glossary.WebsiteMonitoring
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook