Deny repeated, unwanted CONNECT/POST requests

[lesterofpupets]

Hello all. I get a LOT of these (and approximates of these...)

CONNECT 195.169.138.#*$!:7000 HTTP/1.0" 405 235 "-" "-"
POST [195.169.138.#*$!:7000...] HTTP/1.0" 200 1771 "-"

I'm not too fond of the POST request returning a 200.
So, I've inserted a Limit POST directive into my conf file, yet I'm still getting POST requests that get answered with a 200. Could you help me stem the flow of these successful requests? Are they a threat?

Thanks.

Here's a snippet from conf file

<Directory />
Options FollowSymLinks
AllowOverride None

# 2005-11-26. LKL. disallow POST requests
<Limit POST>
Order deny,allow
Deny from all
</Limit>
</Directory>

[jdMorgan]

Since this POST request is directed to another server, the test for "/" required by the <Directory> container is likely to fail. Try moving this access-control code out of any containers except for <Limit> and see if it works better.

Jim

[lesterofpupets]

Hmmm, syntax error on the "Order deny, allow" line now that it's outside <Directory />

[lesterofpupets]

Thanks for your reply jd,

Some light was shed on this matter in an #apache channel...quoted from the manual...

"The purpose of the <Limit> directive is to restrict the effect of the access controls to the nominated HTTP methods. For all other methods, the access restrictions that are enclosed in the <Limit> bracket will have no effect."

Perhaps POST is not a "nominated http method"?

LimitExcept might work.

Will keep the board posted.

[jdMorgan]

No, it's saying that anything within a <Limit POST> container only applies to POST requests, and anything within a <Limit GET> container only applies to GET requests.

Try enclosing your access-control code in some other container, such as <Files> or <Directory> to avoid the whole problem.

Jim