-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Leon,
Leon Rosenberg wrote: > Having said that, there are a lot of use cases where you explicitelly > don't want google or anyone else to index the site, cause it contains > private information, would you like to see your private emails or your > health check or your account's balance sheet in google, and would you > like other people to see it? For those cases it's completely > irrelevant whether the site is easy-index-able or not, and doesn't > influence your framework decision. ... and just as easy to use a robots.txt file to disable (legitimate) search engine indexing. I would argue that protected content should be ... protected anyway, and not indexable at all, regardless of robot.txt status. > Craig McClanahan once said, that probably 90% of struts applications > worldwide are running behind company firewalls in intranets. How > relevant is indexing for those? (And yes, I know that they can buy > google appliance and index them privately :-)) I'm not sure the Struts example is relevant, here, since Struts doesn't use single-URL semantics. Or, at least, it does not encourage these semantics. > To sum it up, there are a lot of homework you have to perform if you > want your site properly indexed, and using a framework which hides > everything behind one url and sends POST requests is surely contra > productive. Absolutely. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjJPssACgkQ9CaO5/Lv0PCbkACgj9VKg7W1IXqoYMQhK08gQ+Ta +1AAoIaZXQGAhkrpcJ7shjN/GidDQqXB =MVss -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
