On Thu, 28 Jan 2010 14:47:08 -0200, Ville Virtanen
<ville.virta...@cerion.fi> wrote:
Hi,
Hi!
One way to prevent this is to contribute a T5 httprequest filter that
just redirects to error page if it detects a post url submitted using
GET.
Well, Tapestry always submit by POST, so any submission using GET is not
an human user.
If you want to provide access to robots, I think it's better to have some
kind of API linke Twitter has.
(And isn't hrx?)
hrx? I guess I need some more internet vocabulary . . . hehehe
This is one of the T5 weaker sides I think. It produces many
like these in the production for us for a site that slightly altered url
layout, although these errors are rarely made by human.
I think this is an upside, not a downside, as it shows that suspicious
requests are being made.
Haven't seen that one on our production servers, however our servers are
getting hammered by someone trying to get /index.html which produces
"there is no such component in page... blah .. the valid components
are...".
This can be fixed by implementing a component named html that does
absolutely nothing and placing it to the page.
You could also have an URL rewriter rule to catch that.
- Ville (From f*cking cold and snowy Turku ;))
Thiago (from f*cking-but-not-that-much hot Belo Horizonte) ;)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
