On May 7, 3:46 pm, WebbedIT <[email protected]> wrote: > > I guess you've never heard of black hat seo techniques. > > Yip, certainly have > > > Report them for what - most of the time we're talking about typos > > A typo wouldn't lead to this issue, a typo would lead to your domain > or main parameters being wrong which would result in CakePHP kicking > out some sort of error. I can't see how anyone would accidentally > type an extra forward slash and then add extra params
I find you insistence that in no normal circumstances could massl have a point (which is how I understand your replies to this thread) - a bit weird. have you never clicked on a link in a forum/email/whatever and got part of the message appended to the url? here, try this one E.g. The book's full of useful info, it's all here http://book.cakephp.org/view/875/x1-3-Collection/and guess what my space bar's a bit dicky. > > > you should /consider/ malicious users (and good luck with reporting > > "the site" - the links will be comment spam - all across the web - > > pointing at you, you can't report "the internet"). > > I bow down to this point, if someone mounts a campaign against a site > then they are likely to use bots and comment spam so the links would > not be from the site of the person conducting the campaign. However, > you could block the offending sites accepting comment spam and contact > the owner of the site, but this would quickly become tedious as it's > not going to stop the malicious idiot sending the comment spam. > > However I still think the chances of someone resorting to such action > against your average site would be few and far between, but agree that > this is something that people should be aware of. I wouldn't want > newbies or anti-cakephp peeps to see this thread and cause widespread > hysteria that CakePHP is crap as any site running on it is going to > under attack from such premeditated malicious attacks. > > > > Now can you remove them links from the net please!!! > > > Sure, they're scheduled to be removed in 2020 > > No seriously, remove them ... you did not need to search out and use > my real site to prove your point I find your opinion in this thread and massive overreaction to my example (seek out? I typed your nick in google and appended example texts to the first hit) contradictory/hypocritical. The main reason for using your own site was: 1) to demonstrate it's easily possible (out of curiosity why isn't your site using the stock pages controller?) 2) to demonstrate that you and google aren't the people with the 'control' to make the problem arise - which to me is the most important reason to consider defending against it. > and whilst I respect your wealth of > Cake development knowledge and what you give to the community I think > that was a pretty crappy thing to do just to prove a point. I'm sorry you feel you've been wronged it was just an example to clearly demonstrate the opposite of your message. Given you emailed me offlist (contrary to popular belief I don't sleep plugged into the internet) I see you really do feel strongly about it - which further confuses me as to why you insist massl's thread is to address a problem that doesn't exist (despite him requesting that whether it exists not be discussed) However, to bring things back to the original point - IMO defending against malicious users isn't the main reason you'd consider the (same content - different url) problem. Here's some example urls that an app can easily generate, one way or another, and they'll all contain the same content: 1) You define some vanity/i18n routes, consider an action in a plugin controller: http://example.com/action/ http://example.com/plugin/action/ * http://example.com/plugin/plugin/action/ http://example.com/plugin/plugin/action/something <- massl's concern 2) You use pagination http://example.com/controller/ http://example.com/controller/index/ http://example.com/controller/index/sort:id/ http://example.com/controller/index/sort:created/ http://example.com/controller/index/page:1/ http://example.com/controller/index/page:1/sort:asc/ http://example.com/controller/index/sort:asc/page:1/ etc. If you insist that it's impossible for someone to maliciously or accidentally append something to a url which your code will ignore - you should at least consider how your own code is generating links. It's possible with some forethought to forgo the entire problem - by using a canonical metatag as lucca suggested and/or by using a component to apply some intelligent 301 redirect logic for you. anyway, hth, AD * with latest 1.3 it doesn't automatically do/understand this any more Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
