: that's not what I mean. api/ should die. but I'm ok with api-3 that points
Well then you and i have radically differnet opinions about SEO and good long term URL practices. it's one thing to say that a URL like "/java/2_9_0/.../Foo.html" should be allowed to start 404ing once the 2.9.0 release is considered "too old" and the docs are taken off the site. but "/solr/api/.../Foo.html" is very differnet -- since Solr 1.1 it has always pointed to the *current* javadocs for that class, and is heavily linked to from the wiki, blogs, bookmarks, and search engines. The fact that we now provide copies of multiple versions of the javadocs is no reason to kill off a bunch of useful and valid URLs that have a lot of PageRank value and link juice. If individual class files are removed then sure: those individual pages will, and should, start 404ing because the specific class being refrenced no longer exist, but on the whole there is no reason not to continue to the basic path redirect -- It takes about 60 seconds of effort to toggle ~6 bytes of the .htaccess file to keep those URLs pointed at the "current" release. As long as someone like me is willing to do the work when new releases come out, there is no reason for all those links to "die" -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
