RE: Baffling Error

2008-03-21 Thread Mark Leder
12:11 PM To: CF-Talk Subject: Re: Baffling Error Somebody has a bad link to your site? ~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk

Re: Baffling Error

2008-03-21 Thread Gerald Guido
This might be the culprit. http://weblog.infoworld.com/securityadviser/archives/2008/03/organized_crimi.html?source=NLC-DAILYcgd=2008-03-21 On Thu, Mar 20, 2008 at 11:38 AM, Mark Leder [EMAIL PROTECTED] wrote: Hi, I've been going through my error logs on CF8/IIS6, and repeatedly come up

Baffling Error

2008-03-20 Thread Mark Leder
Hi, I've been going through my error logs on CF8/IIS6, and repeatedly come up with this message (note the URL will be for any site that's on my server, this is an example): http://rosemariespeaks.com/'http:/rosemariespeaks.com/index.cfm The filename, directory name, or volume label

Re: Baffling Error

2008-03-20 Thread Matt Williams
Somebody has a bad link to your site? On Thu, Mar 20, 2008 at 10:38 AM, Mark Leder [EMAIL PROTECTED] wrote: Hi, I've been going through my error logs on CF8/IIS6, and repeatedly come up with this message (note the URL will be for any site that's on my server, this is an example):

Baffling Error

2008-03-20 Thread Mark Leder
Hi, I've been going through my error logs on CF8/IIS6, and repeatedly come up with this message (note the URL will be for any site that's on my server, this is an example): http://rosemariespeaks.com/'http:/rosemariespeaks.com/index.cfm The filename, directory name, or volume label

Re: Baffling Error

2008-03-20 Thread C. Hatton Humphrey
I've been going through my error logs on CF8/IIS6, and repeatedly come up with this message (note the URL will be for any site that's on my server, this is an example): I'm with Matt here, it looks like someone, somewhere has a bad link to your site. Your site appears to be functioning

RE: Baffling Error

2008-03-20 Thread Mark Leder
, March 20, 2008 1:04 PM To: CF-Talk Subject: Re: Baffling Error I've been going through my error logs on CF8/IIS6, and repeatedly come up with this message (note the URL will be for any site that's on my server, this is an example): I'm with Matt here, it looks like someone, somewhere has

RE: Baffling Error

2008-03-20 Thread Brad Wood
, 2008 1:09 PM To: CF-Talk Subject: RE: Baffling Error The problem is that there are bots pounding all my sites with malformed urls. I get anywhere from 20 to 100 per day. Is there a way to filter/regex stop that from occuring before it throws an error

Re: Baffling Error

2008-03-20 Thread Claude Schneegans
There is really nothing you can do to stop them. Te prevent them, you're right, but you can definitely stop them, right after the first attempt: Ban the IP! -- ___ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm

Re: Baffling Error

2008-03-20 Thread Gerald Guido
Those are all most likely SQL injection or cross site scripting attack attempts. There is really nothing you can do to stop them. Just make sure all URL data is sanitized before using etc. That is very interesting. Have you run into these a lot? What do these look like? Should ones web server

Re: Baffling Error

2008-03-20 Thread Claude Schneegans
That is very interesting. Have you run into these a lot? What do these look like? I'm having such attempts about a dozen every day, all from different hosts, but all with the same user agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; ..NET CLR 1.1.4322) I

Re: Baffling Error

2008-03-20 Thread C. Hatton Humphrey
The problem is that there are bots pounding all my sites with malformed urls. I get anywhere from 20 to 100 per day. Is there a way to filter/regex stop that from occuring before it throws an error? Create a custom 404 that is caught by both CF and IIS/Apache that redirects to /index.cfm ?

RE: Baffling Error

2008-03-20 Thread Mark Leder
Create a custom 404 that is caught by both CF and IIS/Apache that redirects to /index.cfm ? So, what would the regex or script look like? Because there are lots of variations in the malformed URL. Mark ~| Adobe®