OVH Community, your new community space.

OVH service monitoring


gregoryfenton
21-05-2010, 19:19
the single post

freshwire
21-05-2010, 19:08
Quote Originally Posted by gregoryfenton
eep wrong log file, ignore this post
The post or the whole topic?

gregoryfenton
21-05-2010, 18:12
eep wrong log file, ignore this post

Razakel
21-05-2010, 14:22
Quote Originally Posted by gregoryfenton
Easiest for some, not everyone knows about how to add lines to the index file.
To be honest, I don't think OVH really caters for that sector.

gregoryfenton
21-05-2010, 13:38
Easiest for some, not everyone knows about how to add lines to the index file.

I am not one of them, I have been coding professionally for 21 years this week.

Some people could have (for example) a blog, a non-php enabled server the possibilities are endless. One typo could take their site completely offline (error 500 with apache if you screw up .htaccess springs readily to mind), as well as future upgrades removing the code

freshwire
21-05-2010, 13:24
Yes that would be ideal but usually the easiest to solution is to fix it yourself.

gregoryfenton
21-05-2010, 12:58
Yeah I could have done that, or the person that changed GET // to GET / could change it to HEAD / and it would be systemwide instantly without requiring any changes.

freshwire
21-05-2010, 12:46
Just add a line of code at the top of your page that sends something shorter to that IP.

If your using php:

Code:

gregoryfenton
21-05-2010, 12:22
My server has OVH website service monitoring activated (great service by the way, very handy!)

I am used to seeing the following in my logs:
91.121.5.251 - - [20/May/2010:14:45:02 +0000] "GET // HTTP/1.1" 301 627 "-" "OVH Service Monitoring"

Note the // after GET

I just saw that the format has changed to
91.121.5.251 - - [21/May/2010:11:05:02 +0000] "GET / HTTP/1.1" 200 78192 "-" "OVH Service Monitoring"

As you can see simply by changing GET // to GET / you are served the full page which is taking the size of the page from 627 bytes to 78192 bytes, a 124x increase in size.

The key is the HTTP status code returned - // gives 301 (redirect) where / gives 200 (ok).

May I suggest a HEAD request rather than a GET request which will give a much smaller return packet guaranteed - a GET packet will get the contents of the HEAD as well as the content of the GET.