Re: Tomcat - a search engine liability?!?!

2002-12-12 Thread Craig R. McClanahan
On Wed, 11 Dec 2002, Bill Barker wrote: > Date: Wed, 11 Dec 2002 23:33:43 -0800 > From: Bill Barker <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Tomcat - a search engine liability?!?! > > It's

Re: Tomcat - a search engine liability?!?!

2002-12-11 Thread Bill Barker
the thoughts. > > Neal > > > -Original Message----- > From: Joe Tomcat [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 3:50 PM > To: Tomcat Users List > Subject: RE: Tomcat - a search engine liability?!?! > > > On Wed, 2002-12-11 at 19:19, neal w

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Ralph Einfeldt
least one query parameter are not indexed > -Original Message- > From: neal [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 11:48 PM > To: Tomcat Users List > Subject: Tomcat - a search engine liability?!?! > > > First a conclusion: > 1. Google

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread neal
omcat - a search engine liability?!?! > the SSL certificate is already bound to Tomcat ... I think I'd have to buy > another to work with Apache. Sigh. Don't do it until you prototype your solution and make sure that it works for you. > The primary problem [is] to not

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
> the SSL certificate is already bound to Tomcat ... I think I'd have to buy > another to work with Apache. Sigh. Don't do it until you prototype your solution and make sure that it works for you. > The primary problem [is] to not redirect (http 302) to a different URL, > I want it to stay at ht

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
Joe, > Don't throw in that towel yet! Here's one easy solution: Configure > Tomcat so that .htm pages are handled as jsps. He isn't serving html pages. He is serving mdlx pages, whatever those are, and he wants Google to index them. Supposedly Google doesn't, or this would all be moot. I do w

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread neal
pache. Sigh. Thanks for the thoughts. Neal -Original Message- From: Joe Tomcat [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:50 PM To: Tomcat Users List Subject: RE: Tomcat - a search engine liability?!?! On Wed, 2002-12-11 at 19:19, neal wrote: > Thanks for the suggestions,

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
Neal, > For someone unfamiliar with these things [do] you think > it would be easier to [move] Apache in front of it, or > is it easier to write [a Filter?] I would be comfortable with either, but I've already apache as the front end and experience with mod_rewrite, so I'd go for the 30 second so

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Joe Tomcat
On Wed, 2002-12-11 at 19:19, neal wrote: > Thanks for the suggestions, I'll definitely have to look into them. > > For someone unfamiliar with these things those mod_rewrite or filters do you > think it would be easier to just throw in the towel on using tomcat for http > serving and move Apache i

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
> > The difference is that servlet mapping doesn't allow regex replacement, > > whereas mod_rewrite allows: > > RewriteRule ^(.*)/mdlx/(.*).html$ $1/$2.mdlx > Or implement the equivalent remapping in a Filter if you'd prefer a > pure-Java solution. It's pretty easy to do -- and you can even use

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread neal
- a search engine liability?!?! On Wed, 11 Dec 2002, Noel J. Bergman wrote: > Date: Wed, 11 Dec 2002 20:15:32 -0500 > From: Noel J. Bergman <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subj

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Craig R. McClanahan
On Wed, 11 Dec 2002, Noel J. Bergman wrote: > Date: Wed, 11 Dec 2002 20:15:32 -0500 > From: Noel J. Bergman <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: Tomcat - a search engine

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
, 2002 19:47 To: 'Tomcat Users List' Subject: RE: Tomcat - a search engine liability?!?! This is certainly no long term and all encompassing solution, but if you had certain Servlets you wanted indexed by a search engine, you can map almost any URL to a servlet in the web.xml. Check servle

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Madere, Colin
a servlet class of "com.company.mycode.SomeServlet". > -Original Message- > From: Noel J. Bergman [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 6:25 PM > To: Tomcat Users List > Subject: RE: Tomcat - a search engine liability?!?! >

RE: Tomcat - a search engine liability?!?!

2002-12-11 Thread Noel J. Bergman
> ASP, and JSP were the only dynamic extensions I consistantly > saw that were being indexed. > Google does NOT index any servlet, framework class, or cgi file. I haven't reviewed your facts for accuracy, so take this with a grain of salt. But *IF* the world according to Google is as you say it

Tomcat - a search engine liability?!?!

2002-12-11 Thread neal
I've been working on Search engine optimization this week and I've come to a couple of conclusions and developed a couple of questions. First a conclusion: 1. Google does NOT index any servlet, framework class, or cgi file. If it doesn't end in "jsp" forget about it. My own framework ending in .