Internetseer

[toolman]

Is there any way to block HEAD requests? I have already blocked both of the IP's (in .htacc) this service keeps pounding me with every 15 minutes even after an email to cease and desist. Still they keep on.

From the looks of it one of my so called competitors has set me up with every page in my site to be monitored...how thoughtful of them.

[awoyo]

It seems there is a way to block head requests although I don't remember how, or where I saw any documentation on it, but you can block the user agent, IP, or IP block (or portion thereof) from .htaccess by using either mod_rewrite or mod_access.

Jim

[Kane]

When surfing the Web I came across Toolmans posting on WebmasterWorld.com. In response, we would like to apologize for any inconvenience our remote Web site monitoring company has caused. Second, we are concerned with any inappropriate uses of our Free Web site monitoring Service. Please send your questions to [e-mail].

InternetSeer is the largest remote Web site monitoring company in the world. We currently monitor over 700,000 Web sites. InternetSeer will check your site every hour, 24/7. If your site is not responding, we will immediately dispatch an email to alert you. Then, when connectivity is restored, we will send an email confirming your site is back up.

In addition, InternetSeer will send you a weekly report on the performance of your Web site. This information is useful for confirming your site's day-to-day connectivity. There's no software to install and you can get started in minutes. Why not activate your account now at www.internetseer.com.

[NFFC]

Welcome to wmw Kane,

>Is there any way to block HEAD requests?

Any input?

[volatilegx]

Here's a link to Apache.org which explains how to limit request types:

[httpd.apache.org...]

What I understand is that you can use this type of format:

<Limit HEAD>
Require valid-user
</Limit>

With the above, only users with passwords would be able to make HEAD requests. You would add the above to a .htaccess file or httpd.conf file.

I would recommend putting the above inside a <directory></directory> block if possible.

[volatilegx]

Upon further study of the <limit> directive, you may not be able to limit HEAD requests. You might have to limit GET requests, which would also limit HEAD requests. I think that would be cutting off your nose to spite your face... sorry.