If you have an error handler, then at the top of it test
http_user_agent and, if it turns out to be Slurp, feed them something
that makes them go away, like as Dave suggested a 200 error rather
than showing them whatever your friendly error is.
I've got the same problem and think I'll try this as
-
From: Matt Robertson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 12:03 PM
To: CF-Talk
Subject: Re: Sloppy - Yahoo! Slurp throwing CFerrors
If you have an error handler, then at the top of it test
http_user_agent and, if it turns out to be Slurp, feed them something
that makes them
What Mark is talking about is Slurp putting in its own url vars, if I
read him correctly. I've seen the same thing. When I first saw it I
thought it was someone hacking. Heck, it still might be.
Amen to using errors to detect site flaws. Reminds you of stuff like
the need to handle, for
-Talk
Subject: Re: Sloppy - Yahoo! Slurp throwing CFerrors
What Mark is talking about is Slurp putting in its own url vars, if I
read him correctly. I've seen the same thing. When I first saw it I
thought it was someone hacking. Heck, it still might be.
Amen to using errors to detect site flaws
@houseoffusion.com
Sent: Monday, February 21, 2005 10:21 AM
Subject: Sloppy - Yahoo! Slurp throwing CFerrors
Does anyone else see CFerrors from Yahoo's spider / bot Slurp? We
monitor
all CFerrors that are generated on our servers. It seems that Yahoo!
Slurp
is responsible for over 60% of the errors
On Wed, 23 Feb 2005 12:53:01 -0500, Bryan F. Hogan
[EMAIL PROTECTED] wrote:
I
guess when you write the full info to disk you can email yourself that an
error occurred and the basic message with a link to your log or something.
Bingo. I write the files to .html and protect the site they go to
On Wed, 23 Feb 2005 10:59:01 -0700, Jim McAtee [EMAIL PROTECTED] wrote:
cfqueryparam cfsqltype=CF_SQL_NUMERIC value=#Val(url.view)#
Holy cow thats simple. Always thought of cfqueryparam as a
replacement for val() in raw sql.
(sound of head bonking repeatedly on wall)
--
--mattRobertson--
If you know that your id must be numeric as in your example, then why
not clean out any non numeric chars before you do anything. That
should remove any extraneous crap added by slurp.
cfset url.id = rereplace([^0-9],url.id,,all)
Or something like that.
On Mon, 21 Feb 2005 14:31:50 -0500,
If you are running Apache, you could use mod_rewrite to change the incoming bad
URLs into good URLs using regular expressions. I don't think IIS has quite as
flexible a tool, but it does have a re-director that you could use per
directory or per URL to forward bad URLs to good URLs.
FYI I have
You could also do the custom 404/error page thing and create a per-URL mapping
to good URLS. If you do that, use header tags to forward to the good URLS with
a 301 Moved Permanently status code. That will tell the bot to stop using the
old URL and use the new one.
FYI I have a custom cf
Does anyone else see CFerrors from Yahoo's spider / bot Slurp? We monitor
all CFerrors that are generated on our servers. It seems that Yahoo! Slurp
is responsible for over 60% of the errors per week that are thrown by our
production webservers. It looks like Slurp is appending almost random
Generally by thworing 404 headers would do it I would think
that tells it that the page that it is asking for does not exist
On Mon, 21 Feb 2005 11:21:42 -0600, Mark W. Breneman
[EMAIL PROTECTED] wrote:
Does anyone else see CFerrors from Yahoo's spider / bot Slurp? We monitor
all CFerrors
]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Monday, February 21, 2005 9:21 AM
Subject: Sloppy - Yahoo! Slurp throwing CFerrors
Does anyone else see CFerrors from Yahoo's spider / bot Slurp? We monitor
all CFerrors that are generated on our servers. It seems that Yahoo! Slurp
is responsible
AM
To: CF-Talk
Subject: Re: Sloppy - Yahoo! Slurp throwing CFerrors
Generally by thworing 404 headers would do it I would think
that tells it that the page that it is asking for does not exist
On Mon, 21 Feb 2005 11:21:42 -0600, Mark W. Breneman [EMAIL PROTECTED]
wrote:
Does anyone else see
How would one go about sending a 500 server error header at
the top of a custom error page? I assume it is more than just
putting 500 server error in the title tag.
Actually, if you have CFMX configured to use HTTP status codes, any uncaught
errors will return an HTTP 500 status code by
Does anyone else see CFerrors from Yahoo's spider / bot
Slurp? We monitor all CFerrors that are generated on our
servers. It seems that Yahoo! Slurp is responsible for over
60% of the errors per week that are thrown by our production
webservers. It looks like Slurp is appending almost
16 matches
Mail list logo
