RE: java.lang.OutOfMemoryError
I was having a similar problem with a similar configuration but was having to restart every day. For some reason the exact same JDK/tomcat install on my windows dev box performed just fine under stress testing and reclaimed memory just fine whereas my Linux production box had serious issues. I increased the memory from the default 64mb to 128mb on my linux server and now it is behaving just as the prod server does - its reclaiming memory in a similar healthy pattern. So, just try increasing the heap size to 128mb first and see if you're still having the same issue. It seems to work some magic. Cheers. Neal -Original Message- From: Marco Pöhler [mailto:[EMAIL PROTECTED] Sent: Sunday, March 21, 2004 4:54 AM To: tomcat-user Subject: java.lang.OutOfMemoryError Hi, I'm running tomcat 5.0.19 J2SDK1.4.2_03 on a suse linux 8.1. I wrote a really simple application, just one servlet and a few jsp pages, using dbcp/jndi. Nevertheless I got an OutOfMemoryError every 2 days and I have to restart the tomcat to fix the problem. Here is the log entry: 2004-03-21 10:41:04 StandardWrapperValve[mapperServlet]: Servlet.service() for servlet mapperServlet threw exception java.lang.OutOfMemoryError Okay, I've investigated my source code for some kind of memory leak, but without any success. How can I found what the problem is ? Are there tools which can help me ? thanks in advance Marco Poehler --- http://www.poehlerpoehler.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Digitally Signing Posts
Ha! I said the same thing a month ago and was completely ignored. :-\ -Original Message- From: Angus Mezick [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 6:44 AM To: Tomcat Users List Subject: RE: Digitally Signing Posts +1 --Angus -Original Message- From: George Sexton [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 8:56 AM To: 'Tomcat Users List' Cc: [EMAIL PROTECTED] Subject: RE:Digitally Signing Posts Would you either A)Not sign posts to the group Or B) Sign the posts with a working certificate? Everytime I hit one of your messages, it locks my mail client up for 30 seconds. Warning: The Certificate Revocation List needed to verify the signing certificate is either unavailable or it has expired. Signed by [EMAIL PROTECTED] using RSA/SHA1 at 12:48:09 AM 3/16/2004. -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:48 AM To: Tomcat Users List Subject: Re: Load balancing for uptime Hi, To keep it up, you will need to setup session replication (See your Cluster element in server.xml), either in-memory or JDBC. Both are supposed to work. However, that implies several things: - Your session must contain Seralizable objects only. - Your performance will be worse (how much worse highly depends on the size of the objects in your session) And... nobody guarantees that your memory leak (if there is one) is not related to the information stored in sessions. Depending on your load balancer, there is another option (IMHO, better for your case). There are some load balancers that allow you to turn a server down while keeping it up for currently established sessions, for a certain time. That allows you NOT to use session replication, thus not replicating any instability related to sessions. Oh, and last, if you need a good consultant for fixing, optimizing or redesigning your application, you just found one ;-) Yours, Antonio Fiol Derek Clarkson wrote: Hi all, We have an app written in a mix of JSP, servlets and struts across 3 instances of apache, tomcat and an RMI server. To say that it's a pile of smelly stuff is an understatement, however it works (mostly) and our customers depend on it. At least once a week though it crashes with out of memory errors. Until we can redesign and fix it we are looking for a way to keep it up. One suggest has been to have two servers running with a common DB server, and to use a load balancer to allow us to keep one server up whilst we boot the other, then vice versa. Thus on a daily basis we can reboot both machines whilst mainting a working system for the users. Can anyone see any problems with this ? I'm concerned about issue realed to session management, etc. Ciao Derek _ _ This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not use, copy or disclose its content to anyone. You must not copy or communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Performance question JDBC vs Properties
Any chance you guys would consider NOT sending signed or encrypted emails to the list any more? They always choke my email client and it just doesn't seem necessary for the purpose of an email newsgroup. ;-) Thanks. Neal -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Monday, February 16, 2004 11:40 PM To: Tomcat Users List Subject: Re: Performance question JDBC vs Properties I would write a reload config servlet. It will save you one JDBC access per request. Antonio Fiol Larraquy wrote: Hi all, I've got this doubt. My applicacion uses some properties files to config some events or constants, or whatever, but it's job basically is to map the users click on a JSP, to a servlet and define what class should take this event. So, every request comming to a JSP, will be a search in this file. This is for writing only 1 Servlet. For instance, if an user clicks ShowClients something like this should be written at the file. Where this class is called to do the job. ShowClients=com.jkt.proyect.clients.ShowClients Or ShowProducts: ShowProducts=com.jkt.proyect.products.ShowProducts This file, should be as big as use cases in the system. Actually we've written 2000 lines. My problem, is that for reconfiguring this file, or adding lines to it, I've got to reload the application. As we are at deploying time, this happens quite often, so I've got to take users out of the system, and then, calling them to continue working (they are quiete few until next month). I'm thinking of sending to logic to a database, I mean configure this in a table. So if I've got 2000 records in this table, would it be much less performant that writing it in a file, as it is now working? Thanks in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat - Automatically writes a session?
You're kidding? So, by default, I'm writing a freaking session for every single page? That sounds like a colossal waist of resources. Thanks though for the tip! Neal -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 11:46 PM To: Tomcat Users List Subject: Re: Tomcat - Automatically writes a session? You have to specify it on the JSP pages. I can't remember it properly, but it must be something like: @page session=false @ Google for it on the Tomcat site. I think you will find it. Antonio Fiol Neal wrote: Someone just pointed out that my JSPs are have this in the header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ The problem is that I'm not setting any sessions or cookies from the page so I have no idea what's going on. Is there some reason this is there? Is there some setting in the Web.xml and/or server.xml file that I must tweak? PS - I use Tomcat has my http server, not apache (in case that's meaningful). Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat - Automatically writes a session?
I used the tag [EMAIL PROTECTED] session=false% which does appear correct, but I'm still seeing that header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ There are two reasons why I want to get rid of this: 1. I assume I'm waiting server resources holding open a session for every user, unnecessarily. 2. I've been told this may prevent Google from properly spidering the site. Can you please shed any more light on how to fix this potential issue? Thanks. N -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 11:46 PM To: Tomcat Users List Subject: Re: Tomcat - Automatically writes a session? You have to specify it on the JSP pages. I can't remember it properly, but it must be something like: @page session=false @ Google for it on the Tomcat site. I think you will find it. Antonio Fiol Neal wrote: Someone just pointed out that my JSPs are have this in the header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ The problem is that I'm not setting any sessions or cookies from the page so I have no idea what's going on. Is there some reason this is there? Is there some setting in the Web.xml and/or server.xml file that I must tweak? PS - I use Tomcat has my http server, not apache (in case that's meaningful). Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat - Automatically writes a session?
Unreal I've done everything I can think of and I'm still seeing a JSession cookie in the header of my pages: I've tried: 1. server.xml file - host/@cookies=false 2. [EMAIL PROTECTED] session=false% as the first line of the JSP. 3. Restarted application numerous times. 4. Absolutely no code to write a cookie or a session ANYWHERE in the entire applcation. Any ideas??! Here's the Header being returned: Server Response: http://www.travelusa.com/hotels.jsp?2 Status: HTTP/1.1 200 OK Set-Cookie: JSESSIONID=FC6ECEFBABA482AE6707EC400E229FB1; Path=/ Content-Type: text/html;charset=ISO-8859-1 Transfer-Encoding: chunked Date: Tue, 20 Jan 2004 10:44:21 GMT Server: Apache Coyote/1.0 Thanks. N -Original Message- From: Neal [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 11:53 PM To: 'Tomcat Users List' Subject: RE: Tomcat - Automatically writes a session? You're kidding? So, by default, I'm writing a freaking session for every single page? That sounds like a colossal waist of resources. Thanks though for the tip! Neal -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 11:46 PM To: Tomcat Users List Subject: Re: Tomcat - Automatically writes a session? You have to specify it on the JSP pages. I can't remember it properly, but it must be something like: @page session=false @ Google for it on the Tomcat site. I think you will find it. Antonio Fiol Neal wrote: Someone just pointed out that my JSPs are have this in the header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ The problem is that I'm not setting any sessions or cookies from the page so I have no idea what's going on. Is there some reason this is there? Is there some setting in the Web.xml and/or server.xml file that I must tweak? PS - I use Tomcat has my http server, not apache (in case that's meaningful). Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat - Automatically writes a session?
Unfortunately this isn't working either. In addition to the [EMAIL PROTECTED] session=false% directive in my JSP, I have also set the cookies=false attribute in my server.xml file, for the host in question. It is *still* happening! Perhaps this is a Tomcat bug, as previously suggested? Correct me if I'm wrong, but doesn't this imply a *HUGE* waist of RAM resources to be writing a cookie like this by default? Why on earth would a web app do this by default? Are there any other ways to shut it off? It was mentioned in the previous thread to look at the servlet being compiled, which may be a good idea - but I don't know what the solution will be if it is in fact compiling the servlet incorrectly. Any other config opps to choke it off? Neal Torsten Fohrer [EMAIL PROTECTED] wrote: tomcat sents automatically a cookie named jsessionid for session maintain to a browser. with cookies=false as a context attrribute you disable this behaviour from tomcat documentation: -- cookies Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application. or http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html cu Torsten Fohrer On Tuesday 20 January 2004 20:58, you wrote: Verify in your JSP's .java file that sessions are really being turned off. Look to see if there is a session=pageContext.getSession() Also, I think the call to pageContext = _jspxFactory.getPageContext(. Needs to have false as the 3rd to last argument. [EMAIL PROTECTED] 1/20/04 12:39:54 PM Neal wrote: I used the tag which does appear correct, but I'm still seeing that header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ There are two reasons why I want to get rid of this: 1. I assume I'm waiting server resources holding open a session for every user, unnecessarily. 2. I've been told this may prevent Google from properly spidering the site. Can you please shed any more light on how to fix this potential issue? Probably not, but I will try... Did you clear the cookies on your browser? If the browser is saying Hi! XXX is my session ID, then, (iif that session exists), tomcat is free of saying Hi! keep your session ID, which is XXX Other than that, no idea. I have never struggled to avoid cookies. Sorry. I was only echoing something I have read in the past. Antonio Fiol Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
Re: Tomcat - Automatically writes a session?
Which tool are you guys using to view your http response header? I'm using the following: http://www.searchengineworld.com/cgi-bin/servercheck.cgi Do you see the cookie being set using this tool? What sort of filters should I be looking for that could be setting a cookie? btw - my config is just straight Tomcat 4.1, no Apache. If you want to see an example of what I'm seeing, please go to http://www.travelusa.com/. If you can recommend any filters or anything else like that I should be looking at, please let me know. Thanks for your help. Neal Jeff Tulley [EMAIL PROTECTED] wrote: Yeah, I see the same thing. No jsessionId in the header. with session=false % [EMAIL PROTECTED] 1/20/04 3:31:31 PM Its on by default because the spec says so. Are you sure you don't have a filter or anything else creating a session? I created a page called cowbell with this content with tomcat 4.1: -- foo -- Then simulated a web browser: -- [EMAIL PROTECTED]: telnet localhost 8080 Trying 127.0.0.1... Connected to fever.joedog.org. Escape character is '^]'. GET /cowbell.jsp HTTP/1.1 Host: fever.joedog.org:8080 Connection: close HTTP/1.1 200 OK Content-Type: text/html;charset=ISO-8859-1 Content-Length: 5 Date: Tue, 20 Jan 2004 22:28:20 GMT Server: Apache-Coyote/1.1 Connection: close foo Connection closed by foreign host. -- -Tim neal cabage wrote: Unfortunately this isn't working either. In addition to the session=false%directive in my JSP, I have also set the cookies=false attribute in my server.xml file, for the host in question. It is *still* happening! Perhaps this is a Tomcat bug, as previously suggested? Correct me if I'm wrong, but doesn't this imply a *HUGE* waist of RAM resources to be writing a cookie like this by default? Why on earth would a web app do this by default? Are there any other ways to shut it off? It was mentioned in the previous thread to look at the servlet being compiled, which may be a good idea - but I don't know what the solution will be if it is in fact compiling the servlet incorrectly. Any other config opps to choke it off? Neal Torsten Fohrer wrote: tomcat sents automatically a cookie named jsessionid for session maintain to a browser. with cookies=false as a context attrribute you disable this behaviour from tomcat documentation: -- cookies Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application. or http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html cu Torsten Fohrer On Tuesday 20 January 2004 20:58, you wrote: Verify in your JSP's .java file that sessions are really being turned off. Look to see if there is a session=pageContext.getSession() Also, I think the call to pageContext = _jspxFactory.getPageContext(. Needs to have false as the 3rd to last argument. [EMAIL PROTECTED] 1/20/04 12:39:54 PM Neal wrote: I used the tag which does appear correct, but I'm still seeing that header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ There are two reasons why I want to get rid of this: 1. I assume I'm waiting server resources holding open a session for every user, unnecessarily. 2. I've been told this may prevent Google from properly spidering the site. Can you please shed any more light on how to fix this potential issue? Probably not, but I will try... Did you clear the cookies on your browser? If the browser is saying Hi! XXX is my session ID, then, (iif that session exists), tomcat is free of saying Hi! keep your session ID, which is XXX Other than that, no idea. I have never struggled to avoid cookies. Sorry. I was only echoing something I have read in the past. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
RE: Tomcat - Automatically writes a session?
Well, the cookie is written but RAM memory must be allocated for these users as well, right? If you have a timeout set to 30 minutes, you've got a lot of little pieces of RAM being held by these users at any given time. Seems waistful to me, regardless how small they are. It just seems silly to be writing cookies for every page, regardless of whether you need one. Well, no - no I don't use any filters, I do have that directive for no session and I do have the cookies=false in my server.xml. I guess I'll take another look but everything I've been tyring isnt' working. grrr. Mike Curwen [EMAIL PROTECTED] wrote: I think it's slightly unfair to characterise the 'on by default' as a 'huge' waste of resources. As Yoav mentioned, the session object is essentially empty and very small. If you don't use it, it should not be a problem. As for 'RAM resources to write a cookie...', that's accomplished on the client, so no load on our server. Also, because it's on by default, you need to ensure that every single JSP includes the 'no session please' directive. Missing it once will create a session for every user that hits the page. Look for this especially in some sort of 'meta' page (like header.jsp or login.jsp or footer.jsp) which are included in any number of other pages. As for filters, people are referring to any javax.servlet.Filter classes you may have written. -Original Message- From: neal cabage [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 3:48 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: Tomcat - Automatically writes a session? Unfortunately this isn't working either. In addition to the directive in my JSP, I have also set the cookies=false attribute in my server.xml file, for the host in question. It is *still* happening! Perhaps this is a Tomcat bug, as previously suggested? Correct me if I'm wrong, but doesn't this imply a *HUGE* waist of RAM resources to be writing a cookie like this by default? Why on earth would a web app do this by default? Are there any other ways to shut it off? It was mentioned in the previous thread to look at the servlet being compiled, which may be a good idea - but I don't know what the solution will be if it is in fact compiling the servlet incorrectly. Any other config opps to choke it off? Neal Torsten Fohrer wrote: tomcat sents automatically a cookie named jsessionid for session maintain to a browser. with cookies=false as a context attrribute you disable this behaviour from tomcat documentation: -- cookies Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application. or http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html cu Torsten Fohrer On Tuesday 20 January 2004 20:58, you wrote: Verify in your JSP's .java file that sessions are really being turned off. Look to see if there is a session=pageContext.getSession() Also, I think the call to pageContext = _jspxFactory.getPageContext(. Needs to have false as the 3rd to last argument. [EMAIL PROTECTED] 1/20/04 12:39:54 PM Neal wrote: I used the tag which does appear correct, but I'm still seeing that header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ There are two reasons why I want to get rid of this: 1. I assume I'm waiting server resources holding open a session for every user, unnecessarily. 2. I've been told this may prevent Google from properly spidering the site. Can you please shed any more light on how to fix this potential issue? Probably not, but I will try... Did you clear the cookies on your browser? If the browser is saying Hi! XXX is my session ID, then, (iif that session exists), tomcat is free of saying Hi! keep your session ID, which is XXX Other than that, no idea. I have never struggled to avoid cookies. Sorry. I was only echoing something I have read in the past. Antonio Fiol Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
RE: Tomcat - Automatically writes a session?
Thanks for the tip. I'll definitely check it out. I've heard its a lot better for javascript debugs as well. Mike Curwen [EMAIL PROTECTED] wrote: I like using Mozilla for cookie inspection. Its setup screens let you clear your cookie cache, inspect cookies on your system, and accept/deny each cookie sent to you, as they are sent to you, including jsessionid 'session' cookies. -Original Message- From: neal cabage [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 5:00 PM To: Tomcat Users List Subject: Re: Tomcat - Automatically writes a session? Which tool are you guys using to view your http response header? I'm using the following: http://www.searchengineworld.com/cgi-bin/servercheck.cgi Do you see the cookie being set using this tool? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
Tomcat - Automatically writes a session?
Someone just pointed out that my JSPs are have this in the header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ The problem is that I'm not setting any sessions or cookies from the page so I have no idea what's going on. Is there some reason this is there? Is there some setting in the Web.xml and/or server.xml file that I must tweak? PS - I use Tomcat has my http server, not apache (in case that's meaningful). Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
I went through th process of applying the new Level 2 3 certs to my cacerts file using the Java Keytool and the output of the keytool seems to have implied this was done correctly but I'm still getting the same error when attempting to retrieve a document over https (SSL): javax.net.ssl.SSLHandshakeException: Could not find trusted certificate. Moreover, it appears that the lib/security/cacerts file doesn't even exist on my Linux production server...only on my Windows Dev server. linux instead has some .crt files in the /bin directory. Anyone have any recommendations? One thing mentioned on the Sun site was to upgrade the JDK to a version with updated certs. Should I worry about this corrupting my own SSL certs? And how difficult is this sort of an update on Linux (I'm a little Linux- phobic). Thanks. - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
I suddenly have a problem reading XML over SSL, where the system has
been in place for a year and the problem never existed before! And the
weird part is
that both my dev and production environmets now seem to have the same
problem.
Another interesting tidbit I have noticed is that I *can* access XML
documents on my own server (using a Thawte cert) but have a problem when
attempting to access documents on two external servers that I know use
Verisign certs. This may or may not be related.
Can anyone think of what may be wrong or what I can do to correct the
issue?
I am getting the following error:
javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
Here is the method I am using to retrieve the document:
public Document readDocument(URL url) throws IOException,
ParserConfigurationException, SAXException {
Document doc = null;
InputStream in = url.openStream();
DocumentBuilderFactory docBuilderFactory =
DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
doc = docBuilder.parse(in);
return doc;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
I suddenly have a problem reading XML over SSL, where the system has
been in place for a year and the problem never existed before! And the
weird part is that both my dev and production environments now seem to
have the same problem.
Another interesting tidbit I have noticed is that I *can* access XML
documents on my own server (using a Thawte cert) but have a problem when
attempting to access documents on two external servers that I know use
Verisign certs. This may or may not be related.
Can anyone think of what may be wrong or what I can do to correct the
issue?
I am getting the following error:
javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
Here is the method I am using to retrieve the document:
public Document readDocument(URL url) throws IOException,
ParserConfigurationException, SAXException {
Document doc = null;
InputStream in = url.openStream();
DocumentBuilderFactory docBuilderFactory =
DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder =
docBuilderFactory.newDocumentBuilder();
doc = docBuilder.parse(in);
return doc;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: RES: javax.net.ssl.SSLHandshakeException: Could not find trusted certificate
What page at Verisign were you reading this from?
Thanks.
Neal
Mauro Pencov [EMAIL PROTECTED] wrote:I was reading in the site of the Verisign, I
found the page that offers for
download Intermediate CA, but this would be used for Apache. And in tomcat?
Somebody already it made this in the Tomcat? Which the process?
( https://www.verisign.com/support/site/caReplacement.html )
-Mensagem original-
De: Alexander Taler [mailto:[EMAIL PROTECTED] nome de Alexander Taler
Enviada em: terca-feira, 13 de janeiro de 2004 14:46
Para: Tomcat Users List
Assunto: Re: javax.net.ssl.SSLHandshakeException: Could not find trusted
certificate
Perhaps it's related to the Verisign intermediate signing
certificate which expired last week. Check the Verisign website
for details.
Alex
Neal == Neal writes:
Neal To: 'Tomcat Users List'
Neal Subject: javax.net.ssl.SSLHandshakeException: Could not find trusted
Neal certificate
Neal Date: Mon, 12 Jan 2004 23:05:41 -0800
Neal I suddenly have a problem reading XML over SSL, where the system has
Neal been in place for a year and the problem never existed before! And
the
Neal weird part is that both my dev and production environmets now seem
to
Neal have the same problem.
Neal Another interesting tidbit I have noticed is that I *can* access XML
Neal documents on my own server (using a Thawte cert) but have a problem
Neal when attempting to access documents on two external servers that I
know
Neal use Verisign certs. This may or may not be related.
Neal Can anyone think of what may be wrong or what I can do to correct
the
Neal issue?
Neal I am getting the following error:
javax.net.ssl.SSLHandshakeException:
Neal Could not find trusted certificate
Neal Here is the method I am using to retrieve the document: public
Document
Neal readDocument(URL url) throws IOException,
ParserConfigurationException,
Neal SAXException {
Neal Document doc = null;
Neal InputStream in = url.openStream(); DocumentBuilderFactory
Neal docBuilderFactory =
Neal DocumentBuilderFactory.newInstance();
Neal DocumentBuilder docBuilder =
Neal docBuilderFactory.newDocumentBuilder();
Neal doc = docBuilder.parse(in); return doc;
Neal }
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Do you Yahoo!?
Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
global.asa - Web.xml
I'm trying to do something as simple as define global constants for my JSP application. In ASP there is a Global.asa file and the closest thing in JSP is of course the web.xml file. I defined a value in my web.xml file and assumed I could retrieve it using the following line: String test = (String) new InitialContext().getAttribute(html.basepath); I've done something similar for Datasources that works just fine but for some reason tyring to retrieve a basic String in a similar manner doesn't work. Can someone please tell me what I am missing? Thanks. - Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing
RE: global.asa - Web.xml
Oops, you're right that line would not have compiled...I meant I use this: DataSource ds = (DataSource) new InitialContext().lookup(application.getInitParameter(db.jndi.dsn)); ...to get a datasource values and assumed the similar line would work for retrieving a String: String str = (String) new InitialContext().lookup(application.getInitParameter(myString)); ...but no dice. God, why does it have to be so difficult to do something so simple. I love Java for a lot of reasons, but this kinda stuff makes me really curse it at times. Ok, so you're saying go and read JNDI documentation and hopefully once I understand JNDI inside and out I can finally set a freaking application constant paramter? Shapira, Yoav [EMAIL PROTECTED] wrote: Howdy, I'm trying to do something as simple as define global constants for my JSP application. In ASP there is a Global.asa file and the closest thing in JSP is of course the web.xml file. I defined a value in my web.xml file and assumed I could retrieve it using the following line: String test = (String) new InitialContext().getAttribute(html.basepath); I've done something similar for Datasources that works just fine but for some reason tyring to retrieve a basic String in a similar manner doesn't work. Can someone please tell me what I am missing? You're missing a lot. You should read the Servlet Specification, specially the section on context parameters (context-param elements in web.xml), which is what you will probably use for simple strings. You should read the JNDI documentation for what a context (including InitialContext) is. It doesn't have a getAttribute method, so I seriously doubt this line of code even compiles, much less works for datasources or any other type of JNDI resource. You could use a JNDI context for simple strings, but that's usually overkill. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing
Re: global.asa - Web.xml
Ah, thanks Ben. Yes, I tried what I wrote prior and also tried application.getAttribute ... but didn't realize there was a getInitParameter() method. That did the trick. Thanks. N Ben Souther [EMAIL PROTECTED] wrote: In your web.xml file: city_name NY In your JSP City: On Monday 15 December 2003 02:40 pm, you wrote: I'm trying to do something as simple as define global constants for my JSP application. In ASP there is a Global.asa file and the closest thing in JSP is of course the web.xml file. I defined a value in my web.xml file and assumed I could retrieve it using the following line: String test = (String) new InitialContext().getAttribute(html.basepath); I've done something similar for Datasources that works just fine but for some reason tyring to retrieve a basic String in a similar manner doesn't work. Can someone please tell me what I am missing? Thanks. - Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing
RE: google yourself
If it's really such a big deal, why not just be somewhat anonymous? Use a temp email account and an alias. -Original Message- From: David [mailto:[EMAIL PROTECTED] Sent: Sunday, December 14, 2003 4:18 AM To: 'Tomcat Users List' Subject: RE: google yourself Hi guys, I was facing the same problem myself as well. Whatever I post on the mailing list seems to be searchable through google. Dave suggested not posting to a public list. How can we know if the list we are posting to is a public list or not ? Regards David -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Sunday, December 14, 2003 6:56 AM To: Tomcat Users List Subject: Re: google yourself phil campaigne wrote: Nikola Milutinovic wrote: Ostad, James wrote: have you googled yourself at goole.com? I don't know how they get all of our listserv communications. There is a web archive of this list. What if you don't want everyone in the world to know your business? Don't post to a public list. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How can we know Tomcat is running or not through Standalone Java Prog
Look in your Tomcat/conf/server.xml file. Is there an uncommented service tag like the following? Service name=Tomcat-Standalone This instructs Tomcat to run standalone. Also, you can confirm this by looking at Tomcat output when it is stated. When tomcat starts it will write to standard out (logs in Unix or output window on Windows). -N -Original Message- From: dakavara [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2003 10:42 PM To: Tomcat Users List (E-mail) Subject: How can we know Tomcat is running or not through Standalone Java Prog Hi, How can we know Tomcat is running or not through Standalone Java Program. Thanks in Advance, Ashok.D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSP Editors
Isn't netBeans now SunOne? And don't they now charge an arm and a leg for it? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, November 28, 2003 6:46 AM To: Tomcat Users List Subject: Re: JSP Editors Try netbeans. Its free. And you can debug jsp's in the ide. - Original Message - From: Duncan [EMAIL PROTECTED] To: Tomcat User List [EMAIL PROTECTED] Sent: Friday, November 28, 2003 4:54 AM Subject: JSP Editors Sorry if off topic but... What do people use to edit JSPs? I'm after an editor, free if possible, to run on windows, with syntax colouring and possibly auto complete for java. Have tried vim for windows, but it doesn't seem as nice on windows as it is on linux. Any other suggestions? Cheers Duncan Smith Decker Telecom Ltd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.545 / Virus Database: 339 - Release Date: 11/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Garbage Collection issues
When I said that surely it can't be a memory leak in my app I was operating under the assumption that the JRE runs garbage collection periodically anywayis this not true? If I was waisting resources and not releasing them in a way that the GC could take them back when it runs automatically then why would it take them back when I call garbage collection explicitly? To me, this suggested more of a systemic issue. It was suggested by someone last night that I may want to look at some config lines to make sure GC is active and this seemed in line with my assumption. Is there something else here that I may be missing however? Can you see a possible explanation as to why my app's waisted resources would not get cleaned up until I explicitly ran GC? Thanks. Neal Shapira, Yoav [EMAIL PROTECTED] wrote: Howdy, Perhaps you are experiencing higher load, which requires more memory. Or perhaps your application does have a memory leak: those are possible and occur in java, so yes that would a programming error on your part. The garbage collector does much magic, but it can't save you all the time. You may wish to read up on java memory leaks, as they've been discussed at length on this list and on the net in general. Note that when you call Runtime#gc that's only a suggestion to the JVM: many times when you call that the garbage collector may not run at all. Yoav Shapira Millennium ChemInformatics -Original Message- From: Neal [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2003 8:21 PM To: 'Tomcat Users List' Subject: Garbage Collection issues My Tomcat 4.1 (hosted on Linux) seems to have a problem in recent months with crashing due to unavailable free RAM. Specifically I get a java.error.outOfMemory exception. If check the RAM available (Runtime.getRuntime().totalMemory()), I can see it ticking down through the week. If explicitly run garbage collection however my RAM totally frees up and all is well (Runtime.getRuntime().gc();). Why would this happen? Surely this isn't due to a programming error on my part, otherwise, the resources should automatically released whenever the JRE performs periodic garbage collection. Isn't that correct? Anyone have any theories as to what this may mean and what the best solution would be? Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Free Pop-Up Blocker - Get it now
Garbage Collection issues
My Tomcat 4.1 (hosted on Linux) seems to have a problem in recent months with crashing due to unavailable free RAM. Specifically I get a java.error.outOfMemory exception. If check the RAM available (Runtime.getRuntime().totalMemory()), I can see it ticking down through the week. If explicitly run garbage collection however my RAM totally frees up and all is well (Runtime.getRuntime().gc();). Why would this happen? Surely this isn't due to a programming error on my part, otherwise, the resources should automatically released whenever the JRE performs periodic garbage collection. Isn't that correct? Anyone have any theories as to what this may mean and what the best solution would be? Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSP Editors
Ha! That thing (SunOne) is the bulkiest, heaviest app I've ever installed on my machine. I have to wait minutes for it to start up and a good 30 seconds when intellisense recognizes a new class. Besides, didn't Sun start charging some crazy price for it recently? Use to be free but I think now it's like $500. -Original Message- From: LEONARDO MARTINEZ [mailto:[EMAIL PROTECTED] Sent: Friday, November 28, 2003 7:57 AM To: Tomcat Users List Subject: RE: JSP Editors SunOne CE (nice, based on NetBeans) NetBeans ^ | You cant download this IDE from java.sun.com Jcreator.com Best Regards Leonardo Martinez From Chile -Mensaje original- De: David Sierra Fernández [mailto:[EMAIL PROTECTED] Enviado el: Viernes, 28 de Noviembre de 2003 09:15 Para: Tomcat Users List Asunto: RE: JSP Editors ¿Any of this editors you mentioned (or other)supports step by step debbuging in JSP ¿or simply debugging? David Sierra Fernández e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Mensaje original- De: Shanta B [mailto:[EMAIL PROTECTED] Enviado el: viernes, 28 de noviembre de 2003 11:35 Para: ''Tomcat Users List' ' Asunto: RE: JSP Editors JIDEA is also best .by using this u can go through internal java scource code and also option to remote debug ur servlets by using tomcat -Original Message- From: Bodycombe, Andrew To: 'Tomcat Users List' Sent: 28/11/2003 3:48 PM Subject: RE: JSP Editors www.jedit.org www.eclipse.org Both are free and up to the task. Andy -Original Message- From: Duncan [mailto:[EMAIL PROTECTED] Sent: 28 November 2003 09:54 To: Tomcat User List Subject: JSP Editors Sorry if off topic but... What do people use to edit JSPs? I'm after an editor, free if possible, to run on windows, with syntax colouring and possibly auto complete for java. Have tried vim for windows, but it doesn't seem as nice on windows as it is on linux. Any other suggestions? Cheers Duncan Smith Decker Telecom Ltd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat JSP/HTML caching
Is there anyway to cache the output of JSP and HTML pages served by Tomcat or do I need an HTTP server for this (e.g. Apache, IIS)? I have a site begin hosted by Tomcat Standalone which relies upon XML web services to render the contents and consequently the page render time is really slow. Please let me know if there's solution. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Number of instances with SingleThreadModel
Does anyone know how I can check to see how much memory is in use or available on Tomcat at any point in time? I've been getting a java.error.OutOfMemory error lately and I need to be able to track what's going on. Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to monitor RAM Usage
Does anyone know how I can montior RAM usage/availability on Tomcat at any given time? I'm currently having a problem wherein Tomcat crashes about once per week and gives the error Java.error.OutOfMemory but I can't see any diagnostics by which to establish any patterns. I also can't find this information on the Apache site, after having looked for 1/2 hour. Any thoughts/info would be greatly appreciates. Thanks. Neal - Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
RE: How to monitor RAM Usage
Thanks. How do I issue such a command? Command line, etc? Neal Nathan Mcminn [EMAIL PROTECTED] wrote: Neal, This will get you the total amount of memory available to the JVM tomcat is running in: Runtime.getRuntime().totalMemory() And this will get you the amount free Runtime.getRuntime().freeMemory() Nathan McMinn Application Developer NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] http://www.NequalsOne.com -Original Message- From: neal cabage [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2003 1:07 PM To: Tomcat Users List Subject: How to monitor RAM Usage Does anyone know how I can montior RAM usage/availability on Tomcat at any given time? I'm currently having a problem wherein Tomcat crashes about once per week and gives the error Java.error.OutOfMemory but I can't see any diagnostics by which to establish any patterns. I also can't find this information on the Apache site, after having looked for 1/2 hour. Any thoughts/info would be greatly appreciates. Thanks. Neal - Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
Re: How to monitor RAM Usage
Thanks. Out of curiosity, what sort of RAM allocations would you typically do on a production UNIX machine? Obviously I don't want to use up all of my memory, but this and mySQL are my only two production apps. ' Thanks. Neal James Black [EMAIL PROTECTED] wrote: neal cabage wrote: I'm currently having a problem wherein Tomcat crashes about once per week and gives the error Java.error.OutOfMemory but I can't see any diagnostics by which to establish any patterns. I also can't find this information on the Apache site, after having looked for 1/2 hour. If you use top (on unix) or the taskmanager, on windows, you can see how large it gets. Most likely you will just need to add a java option to catalina.sh try JAVA_OPTS=-mx512m if you want it to grow to 512megs in size. Any thoughts/info would be greatly appreciates. Thanks. Neal - Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
upgrade from 4.0 to 4.1
I tried to do a simple upgrade from 4.0.4 to 4.1.18. I simply copied the file structures of 4.1.18 over the top of those for 4.0.4. I presume this should do it but in fact I now get a message that Tomcat can't find the compiler. It is suggesting that perhaps my JAVA_HOME variable isn't set. But .. it is! And besides I didn't touch my sys variables. Any thoughts? JDK1.4.1 isn't required here is it? Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an endorsed directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Hmm ... it appears that for some F***'ed up reason, that the URL created by using his.getClass().getResource() is no longer acceptable for TRAX when using Tomcat 4.1.18, as compared to Tomcat 4.0.4. The problem is that the URI begins with a /. If I remove that leading / suddenly the URLs are acceptable in Tomcat 4.1.18. Why would Tomcat be involving itself in such issues? Only thing I can think of is that maybe the conditions for this Apache Exception were redefined in 4.1.18: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 11:02 AM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an endorsed directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Hmm ... I'm wondering how this is going to affect the x-platform-ness of my application now. I'm developing on a windows platform and deploying to linux, wherein my paths actually *should* start with a /. UUugh. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Actually, It seems that the problem is that Class.getResource() is returning a URL with a leading / dispite the fact that I'm on a Windows box. For instance, its returning a url like: /D:/dev/tomcat/... where it *should* be returning: D:/dev/tomcat/.. If I mockup a String of that nature it works fine which seems to confirm this. So, I could always compensate by removing the / but I ultimately deploy to Linux and I presume this will mess up my paths in my production site if I do so. Of course, I could always find a workaround ... but ... should I have to? I mean, I'm guessing this is a bug somehow associated with the context of this version of Tomcat. Any thoughts? Thanks. Neal -Original Message- From: Reynir Hübner [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 12:41 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hi, This may have something to do with an upgraded version of jaxp or xerces, distributed with some dists of tomcat. According to the error you're getting your url is missing scheme, often 'http' or 'https' in the beginning of the url (before '://') [scheme:]scheme-specific-part[#fragment] Which version of tomcat did you download (the full version or 1.4. LE) ? Hope it helps -reynir -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: 1. mars 2003 20:36 To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hmm ... it appears that for some F***'ed up reason, that the URL created by using his.getClass().getResource() is no longer acceptable for TRAX when using Tomcat 4.1.18, as compared to Tomcat 4.0.4. The problem is that the URI begins with a /. If I remove that leading / suddenly the URLs are acceptable in Tomcat 4.1.18. Why would Tomcat be involving itself in such issues? Only thing I can think of is that maybe the conditions for this Apache Exception were redefined in 4.1.18: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 11:02 AM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an endorsed directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
If that's normal then why did it work in Tomcat 4.0.4 and not in Tomcat 4.1.18? I can not say positively that it was not adding that leading slash in 4.0.4 but it was the first thing I noticed and when I took it out it fixed the problem. What else could it be? Neal -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 1:24 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) That's normal. The full URL should look soemthing like this, though... file:///D:/dev/tomcat/webapps/myapp/WEB-INF/classes/org/mypackage/somefile.p roperties or if it is inside an archive... jar:file:///D:/dev/tomcat/webapps/myapp/WEB-INF/lib/somejar.jar!/org/mypacka ge/somefile.properties Jake At 01:00 PM 3/1/2003 -0800, you wrote: Actually, It seems that the problem is that Class.getResource() is returning a URL with a leading / dispite the fact that I'm on a Windows box. For instance, its returning a url like: /D:/dev/tomcat/... where it *should* be returning: D:/dev/tomcat/.. If I mockup a String of that nature it works fine which seems to confirm this. So, I could always compensate by removing the / but I ultimately deploy to Linux and I presume this will mess up my paths in my production site if I do so. Of course, I could always find a workaround ... but ... should I have to? I mean, I'm guessing this is a bug somehow associated with the context of this version of Tomcat. Any thoughts? Thanks. Neal -Original Message- From: Reynir Hübner [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 12:41 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hi, This may have something to do with an upgraded version of jaxp or xerces, distributed with some dists of tomcat. According to the error you're getting your url is missing scheme, often 'http' or 'https' in the beginning of the url (before '://') [scheme:]scheme-specific-part[#fragment] Which version of tomcat did you download (the full version or 1.4. LE) ? Hope it helps -reynir -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: 1. mars 2003 20:36 To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hmm ... it appears that for some F***'ed up reason, that the URL created by using his.getClass().getResource() is no longer acceptable for TRAX when using Tomcat 4.1.18, as compared to Tomcat 4.0.4. The problem is that the URI begins with a /. If I remove that leading / suddenly the URLs are acceptable in Tomcat 4.1.18. Why would Tomcat be involving itself in such issues? Only thing I can think of is that maybe the conditions for this Apache Exception were redefined in 4.1.18: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 11:02 AM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an endorsed directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
actually the full URL that's coming back does not have the file:// in front. I guess that's why its complaining about not having a scheme. But again, why did it work before? Why does it not work now? And if the scheme is required, why is Class.getResource() not returning that as part of the URL? -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 1:24 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) That's normal. The full URL should look soemthing like this, though... file:///D:/dev/tomcat/webapps/myapp/WEB-INF/classes/org/mypackage/somefile.p roperties or if it is inside an archive... jar:file:///D:/dev/tomcat/webapps/myapp/WEB-INF/lib/somejar.jar!/org/mypacka ge/somefile.properties Jake At 01:00 PM 3/1/2003 -0800, you wrote: Actually, It seems that the problem is that Class.getResource() is returning a URL with a leading / dispite the fact that I'm on a Windows box. For instance, its returning a url like: /D:/dev/tomcat/... where it *should* be returning: D:/dev/tomcat/.. If I mockup a String of that nature it works fine which seems to confirm this. So, I could always compensate by removing the / but I ultimately deploy to Linux and I presume this will mess up my paths in my production site if I do so. Of course, I could always find a workaround ... but ... should I have to? I mean, I'm guessing this is a bug somehow associated with the context of this version of Tomcat. Any thoughts? Thanks. Neal -Original Message- From: Reynir Hübner [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 12:41 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hi, This may have something to do with an upgraded version of jaxp or xerces, distributed with some dists of tomcat. According to the error you're getting your url is missing scheme, often 'http' or 'https' in the beginning of the url (before '://') [scheme:]scheme-specific-part[#fragment] Which version of tomcat did you download (the full version or 1.4. LE) ? Hope it helps -reynir -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: 1. mars 2003 20:36 To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hmm ... it appears that for some F***'ed up reason, that the URL created by using his.getClass().getResource() is no longer acceptable for TRAX when using Tomcat 4.1.18, as compared to Tomcat 4.0.4. The problem is that the URI begins with a /. If I remove that leading / suddenly the URLs are acceptable in Tomcat 4.1.18. Why would Tomcat be involving itself in such issues? Only thing I can think of is that maybe the conditions for this Apache Exception were redefined in 4.1.18: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 11:02 AM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an endorsed directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Hmm. I hear what you're saying but I would think that if Tomcat uses different forms of URL formats that would be a fundamental backwards-compatability issue. Is this not a concern of the product? :( -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 1:53 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) On Sat, 1 Mar 2003, neal wrote: Date: Sat, 1 Mar 2003 13:29:08 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) actually the full URL that's coming back does not have the file:// in front. I guess that's why its complaining about not having a scheme. But again, why did it work before? Why does it not work now? And if the scheme is required, why is Class.getResource() not returning that as part of the URL? I agree that it's odd to have the leading / there, but it is not necessarily a bug (I haven't checked the details). Tomcat (more specifically, the class loader Tomcat provides for your webapp) must be involved in the resources returned from inside the webapp (i.e. /WEB-INF/classes or /WEB-INF/lib), because only Tomcat knows how and where the actual resources are stored (inside our outside a JAR, perhaps still inside an unpacked WAR file, ...). The only promise you get from ClassLoader.getResource() is that, on that URL instance, you can call openStream() or openConnection() to access the underlying resource. The actual format of the URL (when rendered as a String) is totally up to the class loader. There are no guarantees on what it looks like (and, indeed, various versions of Tomcat have all used different URL formats). In particular, you are *not* promised that you can convert the URL to a string form, and then back into a URL object that can retrieve the resource data, like this: URL origURL = this.getClass().getResource(myresource.properties); InputStream origStream = origURL.openStream(); // Must work or its a bug String origString = origURL.toExternalForm(); URL newURL = new URL(origString); InputStream newStream = newURL.openStream(); // Not guaranteed to work Doing these transformations loses the URLStreamHandler that Tomcat embeds in the URL that is returned by getResource(). When passing on the URL that is returned to other processing code, you should always pass it on as a URL (not as a String), or you must provide an appropriate resolver (such as an EntityResolver instance for a SAXParser, or a URIResolver for a Transformer). Note that if the origURL.openStream() call fails, that's definitely a bug ... but if it works, then the class loader has fulfilled its promise, and its up to you to provide the appropriate URL resolution services if you convert to a String and back again. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Thanks for the info. I guess I'm just frustrated because my app broke when I upgraded Tomcat. :-\ Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 4:36 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) On Sat, 1 Mar 2003, neal wrote: Date: Sat, 1 Mar 2003 13:59:27 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) Hmm. I hear what you're saying but I would think that if Tomcat uses different forms of URL formats that would be a fundamental backwards-compatability issue. Is this not a concern of the product? No ... the external form of the URL returned by getResource() is a private implementation detail, just as the fully qualified class name of the class that implements HttpSession is a private implementation detail. Just because you can see it doesn't mean you should rely on it. The same goes for relying on any other container-specific (or sometimes even version-specific) feature that is not defined in the specs (like the invoker servlet, or the ability to reload a webapp without restarting your server, or tons of other things ...). More important in this particular case is a fundamental principle of understanding how java.net.URL works -- the mechanism that resolves a URL can either be built in (the URLStreamHandler argument passed to one of the constructors) or must be provided externally. You cannot assume that URL -- String -- URL transformations can be done without losing information. See the Java Tutorial's Networking Trail for more info on the URL related APIs. http://java.sun.com/docs/books/tutorial/ :( Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI
I am in the process of upgrading from Tomcat 4.0.4 to 4.1.18 and whereas my app worked just fine on 4.0.4 it now gives me this error when attempting to parse the first XML document: Error parsing pageMap.xml: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Why is an apache tool being used instead of the NDK for parsing my XML doc and why does it think there must be a scheme in the URI? What does this mean anyway? Is it looking for an XML schema or something? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI
What is it about Tomcat 4.1.18 that is different when it comes to XML parsing??? And for that matter, why does any of this matter to Tomcat? There appears to be somehting in the server/libs/catalina.jar file that is causing this problem. My XML config file parses just fine until I add this jar file..then I get that dumb error: Error parsing pageMap.xml: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI -Original Message- From: neal [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 6:08 PM To: Tomcat Users List Subject: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI I am in the process of upgrading from Tomcat 4.0.4 to 4.1.18 and whereas my app worked just fine on 4.0.4 it now gives me this error when attempting to parse the first XML document: Error parsing pageMap.xml: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Why is an apache tool being used instead of the NDK for parsing my XML doc and why does it think there must be a scheme in the URI? What does this mean anyway? Is it looking for an XML schema or something? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 - 302 issue resolved??? (please please please)
Ah. Good to know. Didn't even know about that list. :) Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 8:08 PM To: 'Tomcat Users List' Subject: RE: Tomcat 5 - 302 issue resolved??? (please please please) The BEST PLACE to get your question answered for Tomcat 5 is tomcat-dev, not tomcat-users. The people actually writing the code you are asking about pay attention to tomcat-dev a lot more than tomcat-users. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 5:51 PM To: Tomcat Users List Subject: Tomcat 5 - 302 issue resolved??? (please please please) There was a discussion a month or two ago about fixing the issue wherein Tomcat *redirects* to the welcome page rather than forwarding to it. For instance, www.abc.com would be redirected to www.abc.com/index.html. Was this issue in fact resolved in Tomcat 5.0? I attempted to take a look at the change log but its empty. :( http://jakarta.apache.org/tomcat/tomcat-5.0-doc/CHANGELOG.txt -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 5 - 302 issue resolved??? (please please please)
Ah. Do you know then how long it might be until that sort of thing is implemented? I'm *REALLY* looking forward to it! :) Thanks. Neal -Original Message- From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Barker Sent: Tuesday, January 21, 2003 10:46 PM To: [EMAIL PROTECTED] Subject: Re: Tomcat 5 - 302 issue resolved??? (please please please) The answer for Tomcat 5 is not yet. There seems to be a consensus on the dev list that this will at least be an option, but it will need to be included in the new Mapper that is required to handle the new welcome-page behavior in the current draft of the 2.4 Servlet spec. Turner, John [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... The BEST PLACE to get your question answered for Tomcat 5 is tomcat-dev, not tomcat-users. The people actually writing the code you are asking about pay attention to tomcat-dev a lot more than tomcat-users. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 5:51 PM To: Tomcat Users List Subject: Tomcat 5 - 302 issue resolved??? (please please please) There was a discussion a month or two ago about fixing the issue wherein Tomcat *redirects* to the welcome page rather than forwarding to it. For instance, www.abc.com would be redirected to www.abc.com/index.html. Was this issue in fact resolved in Tomcat 5.0? I attempted to take a look at the change log but its empty. :( http://jakarta.apache.org/tomcat/tomcat-5.0-doc/CHANGELOG.txt -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Did Tomcat5.0 fix the http 302 issue?
There was a discussion a month or two ago about fixing the issue wherein Tomcat *redirects* to the welcome page rather than forwarding to it. For instance, www.abc.com would be redirected to www.abc.com/index.html. Was this issue in fact resolved in Tomcat 5.0? I attempted to take a look at the change log but its empty. :( http://jakarta.apache.org/tomcat/tomcat-5.0-doc/CHANGELOG.txt -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 5 - 302 issue resolved??? (please please please)
There was a discussion a month or two ago about fixing the issue wherein Tomcat *redirects* to the welcome page rather than forwarding to it. For instance, www.abc.com would be redirected to www.abc.com/index.html. Was this issue in fact resolved in Tomcat 5.0? I attempted to take a look at the change log but its empty. :( http://jakarta.apache.org/tomcat/tomcat-5.0-doc/CHANGELOG.txt -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Mod_JK.c not compatiable with version of Apache
Yes, but when I go to the Linux dir it says mod_jk-2.0.43.so is for Apache 2.0.42 (and 2.0.43) It does not appear that a binary version is available that is compatible with Apache 2.0.40 (the version shipping with RedHat Linux 8 by the way). I am suprised this particular build is not available. Is there something I am missing? :( Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 4:44 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.2 /bin/linux/i386/ Browse around in that tree to find others if needed. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 19, 2003 8:57 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Thanks. I've never had to compile anything like this on Linux and am a little hesitant to do so (more of a windows guy to be honost). Do you know of any place that I could locate pre-compiled *compatible* binaries for either apache 2.0.43 or mod_jk 2.0.40? Or some other compatible set? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 18, 2003 1:23 PM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache You need Apache 2.0.43. .42 might work, but .41 and .40 won't. Or, you can build your own. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 6:50 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Does anyone know why I would get this error when installing mod_JK 2.0.43 on Linux 8, with Tomcat 4.1 and Apache 2.0: mod_jk.c not compatible with this version of Apache. I presume that when it refers to the mod_jk.c it is referring to the cmopuled code it derives from the LoadModule command to load the so (?). I downloaded the mod_jk-2.0.43.so from the Apache connectors archives. I just used the same version (but as a DLL) successfully on my windows workstation. Any thoughts? Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:36 PM To: Tomcat Users List Subject: RE: Mod_JK - JkMount Invalid Command John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache like this: SOME_DRIVE:\SOME\PATH\TO\APACHE\BIN\APACHE.EXE -t This will check the syntax of Apache's httpd.conf without starting Apache. Fix the errors, then call it with -t again until you see Syntax OK. The whole process is described in my HOWTO: http://www.johnturner.com/howto/winxp-howto.html While the version I use in my HOWTO is 4.1.18, the configuration steps are identical, just substitute 4.0.4 wherever you see 4.1.18. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:17 PM To: Tomcat Users List Subject: Mod_JK - JkMount Invalid Command I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED
RE: Mod_JK.c not compatiable with version of Apache
Actually, I was just trying to find binaries for compatible versions of either Apache or mod_jk. So, I wanted to find either (a) Apache 2.0.43 or (b) Mod_jk 2.0.40. Perhaps its me and my phobias of doing a src build on Linux (which I barely know) but I am just not comfortable doing a src build. I presume I'd need to download and learn some C compiler to do the task ... and that's on top of barely knowing the OS! Regarding the pedantics, *IF* the current supported version of Apache is 2.0.43 ... shouldn't there be binaries for it? And even if not, should there be binaries of mod_jk for 2.0.40? It seems like an out-of-sync doulbe whammy! :( Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 11:40 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache Sorry, you lost me. You asked for a link to mod_jk for Apache 2.0.43, that's what I gave you. .43 is the supported Apache version. I don't use RPMs, but it should be fairly trivial to upgrade a RH installation with Apache 2.0.40 to .43. Not to be pedantic, but the current official Apache HTTP release is .43, regardless of whether Red Hat is current or not...it seems reasonable to me that another Jakarta project would support that version and not earlier versions. For example: ftp://ftp.cise.ufl.edu/pub/mirrors/redhat-contrib/libc6/i386/httpd-2.0.43-1. i386.rpm Most RH mirrors will have it. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 2:20 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Yes, but when I go to the Linux dir it says mod_jk-2.0.43.so is for Apache 2.0.42 (and 2.0.43) It does not appear that a binary version is available that is compatible with Apache 2.0.40 (the version shipping with RedHat Linux 8 by the way). I am suprised this particular build is not available. Is there something I am missing? :( Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 4:44 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/ release/v1.2.2 /bin/linux/i386/ Browse around in that tree to find others if needed. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 19, 2003 8:57 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Thanks. I've never had to compile anything like this on Linux and am a little hesitant to do so (more of a windows guy to be honost). Do you know of any place that I could locate pre-compiled *compatible* binaries for either apache 2.0.43 or mod_jk 2.0.40? Or some other compatible set? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 18, 2003 1:23 PM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache You need Apache 2.0.43. .42 might work, but .41 and .40 won't. Or, you can build your own. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 6:50 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Does anyone know why I would get this error when installing mod_JK 2.0.43 on Linux 8, with Tomcat 4.1 and Apache 2.0: mod_jk.c not compatible with this version of Apache. I presume that when it refers to the mod_jk.c it is referring to the cmopuled code it derives from the LoadModule command to load the so (?). I downloaded the mod_jk-2.0.43.so from the Apache connectors archives. I just used the same version (but as a DLL) successfully on my windows workstation. Any thoughts? Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:36 PM To: Tomcat Users List Subject: RE: Mod_JK - JkMount Invalid Command John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache
RE: Mod_JK.c not compatiable with version of Apache
Yeah ... I saw that you sent me the link for mod_jk compatible with Apache 2.0.43. But, I already have that. I need binaries for either (a) Apache 2.0.43 or (b) Mod_jk 2.0.40. In this link that you provided there is only a binary for Mod_jk-2.0.43. If I go to the Apache site to download Apache-2.0.43 there are only links to (a) the source or (b) binaries for *Windows*!. I am sure I am probably missing somethinng ... please tell me what it is?!?! Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 11:57 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache There are binaries for Apache 2.0.43, all over the place. http://httpd.apache.org I gave you a link to the binary Red Hat-compatible RPM for 2.0.43 so that you could upgrade your RH 2.0.40 installation. I gave you a link to the binary for mod_jk that is compatible with 2.0.43. Sorry, but I just don't see what else you need. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 2:54 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Actually, I was just trying to find binaries for compatible versions of either Apache or mod_jk. So, I wanted to find either (a) Apache 2.0.43 or (b) Mod_jk 2.0.40. Perhaps its me and my phobias of doing a src build on Linux (which I barely know) but I am just not comfortable doing a src build. I presume I'd need to download and learn some C compiler to do the task ... and that's on top of barely knowing the OS! Regarding the pedantics, *IF* the current supported version of Apache is 2.0.43 ... shouldn't there be binaries for it? And even if not, should there be binaries of mod_jk for 2.0.40? It seems like an out-of-sync doulbe whammy! :( Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 11:40 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache Sorry, you lost me. You asked for a link to mod_jk for Apache 2.0.43, that's what I gave you. .43 is the supported Apache version. I don't use RPMs, but it should be fairly trivial to upgrade a RH installation with Apache 2.0.40 to .43. Not to be pedantic, but the current official Apache HTTP release is .43, regardless of whether Red Hat is current or not...it seems reasonable to me that another Jakarta project would support that version and not earlier versions. For example: ftp://ftp.cise.ufl.edu/pub/mirrors/redhat-contrib/libc6/i386/h ttpd-2.0.43-1. i386.rpm Most RH mirrors will have it. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 2:20 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Yes, but when I go to the Linux dir it says mod_jk-2.0.43.so is for Apache 2.0.42 (and 2.0.43) It does not appear that a binary version is available that is compatible with Apache 2.0.40 (the version shipping with RedHat Linux 8 by the way). I am suprised this particular build is not available. Is there something I am missing? :( Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 4:44 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/ release/v1.2.2 /bin/linux/i386/ Browse around in that tree to find others if needed. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 19, 2003 8:57 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Thanks. I've never had to compile anything like this on Linux and am a little hesitant to do so (more of a windows guy to be honost). Do you know of any place that I could locate pre-compiled *compatible* binaries for either apache 2.0.43 or mod_jk 2.0.40? Or some other compatible set? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 18, 2003 1:23 PM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache You need Apache 2.0.43. .42 might work, but .41 and .40 won't. Or, you can build your own. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 6:50 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Does anyone know why I would get this error when installing mod_JK 2.0.43 on Linux 8, with Tomcat 4.1 and Apache 2.0: mod_jk.c not compatible with this version of Apache. I presume that when
RE: Mod_JK.c not compatiable with version of Apache
See, I knew there was something I didn't understand. Thanks. I'll take a look. :) Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 12:42 PM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache I gave you this link: ftp://ftp.cise.ufl.edu/pub/mirrors/redhat-contrib/libc6/i386/httpd-2.0.43-1. i386.rpm Which is the link to a Red Hat mirror that has the Apache 2.0.43 binary RPM. Any other contrib mirror will have it as well, if there is one closer to you. Installing that would upgrade your Apache to 2.0.43. There are indeed binaries (not in RPM format) for Linux on the Apache site: 1) go here: http://www.apache.org/dyn/closer.cgi 2) choose a mirror site 3) on that mirror site, go to http://some.mirror.site/httpd/binaries/linux/ This is all sys-admin stuff, not really related to Tomcat at all. If you need help with RPM, I would ask on a Red Hat list or check the man pages (man rpm)...I don't use them so I can't tell you the exact command that will install it and upgrade the existing 2.0.40 at the same time. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 3:32 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Yeah ... I saw that you sent me the link for mod_jk compatible with Apache 2.0.43. But, I already have that. I need binaries for either (a) Apache 2.0.43 or (b) Mod_jk 2.0.40. In this link that you provided there is only a binary for Mod_jk-2.0.43. If I go to the Apache site to download Apache-2.0.43 there are only links to (a) the source or (b) binaries for *Windows*!. I am sure I am probably missing somethinng ... please tell me what it is?!?! Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 11:57 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache There are binaries for Apache 2.0.43, all over the place. http://httpd.apache.org I gave you a link to the binary Red Hat-compatible RPM for 2.0.43 so that you could upgrade your RH 2.0.40 installation. I gave you a link to the binary for mod_jk that is compatible with 2.0.43. Sorry, but I just don't see what else you need. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 2:54 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Actually, I was just trying to find binaries for compatible versions of either Apache or mod_jk. So, I wanted to find either (a) Apache 2.0.43 or (b) Mod_jk 2.0.40. Perhaps its me and my phobias of doing a src build on Linux (which I barely know) but I am just not comfortable doing a src build. I presume I'd need to download and learn some C compiler to do the task ... and that's on top of barely knowing the OS! Regarding the pedantics, *IF* the current supported version of Apache is 2.0.43 ... shouldn't there be binaries for it? And even if not, should there be binaries of mod_jk for 2.0.40? It seems like an out-of-sync doulbe whammy! :( Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 11:40 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache Sorry, you lost me. You asked for a link to mod_jk for Apache 2.0.43, that's what I gave you. .43 is the supported Apache version. I don't use RPMs, but it should be fairly trivial to upgrade a RH installation with Apache 2.0.40 to .43. Not to be pedantic, but the current official Apache HTTP release is .43, regardless of whether Red Hat is current or not...it seems reasonable to me that another Jakarta project would support that version and not earlier versions. For example: ftp://ftp.cise.ufl.edu/pub/mirrors/redhat-contrib/libc6/i386/h ttpd-2.0.43-1. i386.rpm Most RH mirrors will have it. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 2:20 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Yes, but when I go to the Linux dir it says mod_jk-2.0.43.so is for Apache 2.0.42 (and 2.0.43) It does not appear that a binary version is available that is compatible with Apache 2.0.40 (the version shipping with RedHat Linux 8 by the way). I am suprised this particular build is not available. Is there something I am missing? :( Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, January 20, 2003 4:44 AM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache http://jakarta.apache.org
RE: Mod_JK.c not compatiable with version of Apache
Thanks. I've never had to compile anything like this on Linux and am a little hesitant to do so (more of a windows guy to be honost). Do you know of any place that I could locate pre-compiled *compatible* binaries for either apache 2.0.43 or mod_jk 2.0.40? Or some other compatible set? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 18, 2003 1:23 PM To: 'Tomcat Users List' Subject: RE: Mod_JK.c not compatiable with version of Apache You need Apache 2.0.43. .42 might work, but .41 and .40 won't. Or, you can build your own. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 6:50 PM To: Tomcat Users List Subject: RE: Mod_JK.c not compatiable with version of Apache Does anyone know why I would get this error when installing mod_JK 2.0.43 on Linux 8, with Tomcat 4.1 and Apache 2.0: mod_jk.c not compatible with this version of Apache. I presume that when it refers to the mod_jk.c it is referring to the cmopuled code it derives from the LoadModule command to load the so (?). I downloaded the mod_jk-2.0.43.so from the Apache connectors archives. I just used the same version (but as a DLL) successfully on my windows workstation. Any thoughts? Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:36 PM To: Tomcat Users List Subject: RE: Mod_JK - JkMount Invalid Command John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache like this: SOME_DRIVE:\SOME\PATH\TO\APACHE\BIN\APACHE.EXE -t This will check the syntax of Apache's httpd.conf without starting Apache. Fix the errors, then call it with -t again until you see Syntax OK. The whole process is described in my HOWTO: http://www.johnturner.com/howto/winxp-howto.html While the version I use in my HOWTO is 4.1.18, the configuration steps are identical, just substitute 4.0.4 wherever you see 4.1.18. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:17 PM To: Tomcat Users List Subject: Mod_JK - JkMount Invalid Command I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Has the patch to prevent the 302 redirect of the default welcome file been included in Tomcat 5? I looked at the possiblity of applying the patch to Tomcat 4 but I have to admit I am not comfortable building Tomcat on a Linux server as this would require me to do. So I am *hoping* that this is a feature in Tomcat 5 (please please please!!!)?!?!?! :) Thanks. Neal -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:34 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Neal, I told you that solution in the context of your avoiding a redirect (302), not in the context of standalone Tomcat. mod_rewrite is an Apache module. http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg38750.html is the start of a thread on patching Tomcat to do a forward instead of a redirect. Matt Parker's latest patch (not the one in the message) was approved, so long as he keeps the default to the current behavior for now. For Tomcat 5, Remy Maucherat plans to include this functionality in the mapper. --- Noel P.S. If someone needs something from me, direct e-mail might be useful if I don't reply to the list promptly. I'm swamped, and sometimes don't have time to get to the tomcat-user folder. This was my first (and probably only) pass today, and I only checked this thread because RewriteRules is one of my fun topics. -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Mod_JK - JkMount Invalid Command
I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Mod_JK - JkMount Invalid Command
John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache like this: SOME_DRIVE:\SOME\PATH\TO\APACHE\BIN\APACHE.EXE -t This will check the syntax of Apache's httpd.conf without starting Apache. Fix the errors, then call it with -t again until you see Syntax OK. The whole process is described in my HOWTO: http://www.johnturner.com/howto/winxp-howto.html While the version I use in my HOWTO is 4.1.18, the configuration steps are identical, just substitute 4.0.4 wherever you see 4.1.18. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:17 PM To: Tomcat Users List Subject: Mod_JK - JkMount Invalid Command I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Mod_JK.c not compatiable with version of Apache
Does anyone know why I would get this error when installing mod_JK 2.0.43 on Linux 8, with Tomcat 4.1 and Apache 2.0: mod_jk.c not compatible with this version of Apache. I presume that when it refers to the mod_jk.c it is referring to the cmopuled code it derives from the LoadModule command to load the so (?). I downloaded the mod_jk-2.0.43.so from the Apache connectors archives. I just used the same version (but as a DLL) successfully on my windows workstation. Any thoughts? Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:36 PM To: Tomcat Users List Subject: RE: Mod_JK - JkMount Invalid Command John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache like this: SOME_DRIVE:\SOME\PATH\TO\APACHE\BIN\APACHE.EXE -t This will check the syntax of Apache's httpd.conf without starting Apache. Fix the errors, then call it with -t again until you see Syntax OK. The whole process is described in my HOWTO: http://www.johnturner.com/howto/winxp-howto.html While the version I use in my HOWTO is 4.1.18, the configuration steps are identical, just substitute 4.0.4 wherever you see 4.1.18. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:17 PM To: Tomcat Users List Subject: Mod_JK - JkMount Invalid Command I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Mod_JK -2.0.43 compatible with Apache 2.0.40?
Should the mod_jk-2.0.43.so be compatible with Apache 2.0.40? Its such a minor build I would presume so but I'm getting an error message to the contrary. :-\ Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:36 PM To: Tomcat Users List Subject: RE: Mod_JK - JkMount Invalid Command John, Your tutorial ROCKS! It turns out there were 4 distinct problems which I was able to identify in part by using the Apache.exe and in part by comparing your steps to the collage I had compiled from other incomplete sources. My primary problem was that mod_jk.dll was not being recognized so I replaced it with the build you were using (mod_jk-2.0.43.dll) and from there is was pretty much home free! Now on to doing the same on the Linux server (I hope its reasonably similar). :) Thanks again. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 11:22 AM To: 'Tomcat Users List' Subject: RE: Mod_JK - JkMount Invalid Command Uncomment those two lines. Then, open up a command window and call Apache like this: SOME_DRIVE:\SOME\PATH\TO\APACHE\BIN\APACHE.EXE -t This will check the syntax of Apache's httpd.conf without starting Apache. Fix the errors, then call it with -t again until you see Syntax OK. The whole process is described in my HOWTO: http://www.johnturner.com/howto/winxp-howto.html While the version I use in my HOWTO is 4.1.18, the configuration steps are identical, just substitute 4.0.4 wherever you see 4.1.18. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:17 PM To: Tomcat Users List Subject: Mod_JK - JkMount Invalid Command I'm trying to setup ModJK for the first time between Apache 2.0 and TOmcat 4.0.4, on Windows 2000. I am stuck with an error I was hoping someone might recognize: It tells me invliad JKMount command. Perhaps mispelled or defined by a module not included in the server configuration. I presume this is because I have commented out these lines: #LoadModule jk_module modules/mod_jk.so #AddModule mod_jk.c But if I *DONT* comment these out, the test configuration window disappears almost as quickly as it appears and I can't see what the problem is. There is nothing being logged, and if I try to start from the Apache Service manager I simply get a message stating The requested operation failed.. Anyone know what's going on? :( Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
request.getContextPath() not working when Tomcat/ Apache
We use request.getContextPath() in a few situations on a current project. Using Standalone Tomcat we're fine to try to navigate to /project/servlet?cmd=abc however Apache doesn't know what do do with this url. I presume that Apache would prefer an absolute path rather than one relative to the tomcat virtual app. Is there a configuration change that must be made or must we dig into the code and change the URLS? I mean, is there a way around this in Apache? Do we need to provide those full absolute URLS or is there some way to configure Apache/Tomcat to know about this context? Thanks Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Require a secure connection
Does anyone know how to *require* that a page be accessed only via a secure connection? For instance, I *can* request a secure connection to a page by going to https://; and the url ... but how do I prevent a user from going to http://; to request that same page? Would this be a proxy thing or is something I can set in Tomcat? Is there something that wouldn't require the overhead of reflecting upon every single request at the Java level? Thanks. neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
Is it known to be buggy on Linux or just Windows? It sounds like its fine and even preferred according to some docs when using Linux/Apache 1.3. Also, I discussed load balancing and it sounds like we're using hardware load balancer so each instance of Apache will have a 1:1 map to its own Tomcat instance. In this case, is using WARP for production purposes a bad idea? Thanks. Neal -Original Message- From: Lajos Moczar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 8:08 AM To: Tomcat Users List Subject: Re: WARP (Apache-Tomcat) One more point is that webapp is just plain buggy, while tried-and-true mod_jk is quite reliable. If you are hosting anything production-quality, I'd go with mod_jk every time. Lajos neal wrote: For anyone interested I just confirmed via a book I bought from Borders that WARP does not support Load balancing. So, for the archives ... WARP (Via the WebApp module) does not support: 1. Load balancing 2. Apache 2.0 (at least with Windows) And contrary to the Apache's own WebApp module site, Windows *IS* supported for 1.3.27 usage ... and its downloadable from the site. Man, Apache should really update this documentation ... I just waisted the majorty of a day figuring this stuff out (anyone from apache listening out there??). ;-) -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 7:58 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Well, I re-installed an older version of Apache (1.3.27) and WARP via mod_webApp seems to work fine nowand that was on Windows! So, I guess the compatability issue was with Apache 2.0. Hmm. That sucks. By the way, it was mentioned on this thread that mod_jk supports load balancing. Is that to say that WARP won't work in a multiple-host scenario?!?! :( Thanks Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 4:04 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Really?!?! But I downloaded it from the win32 archives on the apache site (http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/v4.0.1/bin/win 32/). It even came with the libapr.dll - the library file compile as a windows DLL. Perhaps its just not compatible with Apache 2? -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 3:50 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) On Tue, 14 Jan 2003, neal wrote: Date: Tue, 14 Jan 2003 15:38:55 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: WARP (Apache-Tomcat) This is totally screwey! Does WARP work on Windows or not?!?! My understanding is not. Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- galatea.com Cocoon training, consulting support -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
Actually, I found the mod_webApp module for Apache-Tomcat warp connection. But Apache won't restart now! Grrr. Per the instructions I tooks the webApp.so and the dll and put the in the modules dir (I'm on windows) and added the necesary lines to the config. BUT, in the doc that came with the mod_webApp there is a note that It was reported that sometimes Apache under windows doesn't like the AddModule line in the config file. Please, ofg you can't start your Apache service try commenting that line in your httpd.conf file. Well, I did that but all that does is avoid the issue. Any clue what the problem is? A hunch is telling me to run regsvr32 on the dll. Any thoughts? Thanks. Neal -Original Message- From: enLogica [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 1:58 PM To: Tomcat Subject: WARP (Apache-Tomcat) I am attempting to setup Tomcat 4.1 with Apache 2.0.4. Per the instructions in my book I am suppose to download the Web Application Module for Apache in order to allow these two to talk, but it is not listed on http://modules.apache.org/search. With v.2.0 do I still need to download this mod? If so, where can I find it? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
Hmm ... sounds like we have two seperate (possible) issues here. 1. webApp.so compatability with with Tomcat 2 2. Flakiness on Windows I'm just trying to model the setup on my Windows workstation so I'm not too worried about the second one ... we will eventually deploy to a linux machine Does anyone know about the 1st possible issue though (Apache 2 compatability)? Thanks. Neal -Original Message- From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 2:56 PM To: 'Tomcat Users List' Subject: RE: WARP (Apache-Tomcat) there is a good chance that the warp module is not Apache2 compatiable. Also if I recall the original author never provided any sort of guarantee that it would work under windows. We have used it successfully on HP-UX for over a year without any problems but for windows you should look into using mod_jk. -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 3:47 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Actually, I found the mod_webApp module for Apache-Tomcat warp connection. But Apache won't restart now! Grrr. Per the instructions I tooks the webApp.so and the dll and put the in the modules dir (I'm on windows) and added the necesary lines to the config. BUT, in the doc that came with the mod_webApp there is a note that It was reported that sometimes Apache under windows doesn't like the AddModule line in the config file. Please, ofg you can't start your Apache service try commenting that line in your httpd.conf file. Well, I did that but all that does is avoid the issue. Any clue what the problem is? A hunch is telling me to run regsvr32 on the dll. Any thoughts? Thanks. Neal -Original Message- From: enLogica [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 1:58 PM To: Tomcat Subject: WARP (Apache-Tomcat) I am attempting to setup Tomcat 4.1 with Apache 2.0.4. Per the instructions in my book I am suppose to download the Web Application Module for Apache in order to allow these two to talk, but it is not listed on http://modules.apache.org/search. With v.2.0 do I still need to download this mod? If so, where can I find it? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
This is totally screwey! Does WARP work on Windows or not?!?! On one hand I've read a tutorial wherein the user claims to have setup warp using windos, but on the other I just read the website for webApp module (http://jakarta.apache.org/~jfclere/webapp_docs/index.html) and it states that it is currently not supported on Windows. And this is aside from finding an answer to the question of where this works with Apache 2.0 or not! Anyone out there using WARP or is everyone using mod_JK? Thanks. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 2:47 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Actually, I found the mod_webApp module for Apache-Tomcat warp connection. But Apache won't restart now! Grrr. Per the instructions I tooks the webApp.so and the dll and put the in the modules dir (I'm on windows) and added the necesary lines to the config. BUT, in the doc that came with the mod_webApp there is a note that It was reported that sometimes Apache under windows doesn't like the AddModule line in the config file. Please, ofg you can't start your Apache service try commenting that line in your httpd.conf file. Well, I did that but all that does is avoid the issue. Any clue what the problem is? A hunch is telling me to run regsvr32 on the dll. Any thoughts? Thanks. Neal -Original Message- From: enLogica [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 1:58 PM To: Tomcat Subject: WARP (Apache-Tomcat) I am attempting to setup Tomcat 4.1 with Apache 2.0.4. Per the instructions in my book I am suppose to download the Web Application Module for Apache in order to allow these two to talk, but it is not listed on http://modules.apache.org/search. With v.2.0 do I still need to download this mod? If so, where can I find it? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
Really?!?! But I downloaded it from the win32 archives on the apache site (http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/v4.0.1/bin/win 32/). It even came with the libapr.dll - the library file compile as a windows DLL. Perhaps its just not compatible with Apache 2? -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 3:50 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) On Tue, 14 Jan 2003, neal wrote: Date: Tue, 14 Jan 2003 15:38:55 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: WARP (Apache-Tomcat) This is totally screwey! Does WARP work on Windows or not?!?! My understanding is not. Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
Well, I re-installed an older version of Apache (1.3.27) and WARP via mod_webApp seems to work fine nowand that was on Windows! So, I guess the compatability issue was with Apache 2.0. Hmm. That sucks. By the way, it was mentioned on this thread that mod_jk supports load balancing. Is that to say that WARP won't work in a multiple-host scenario?!?! :( Thanks Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 4:04 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Really?!?! But I downloaded it from the win32 archives on the apache site (http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/v4.0.1/bin/win 32/). It even came with the libapr.dll - the library file compile as a windows DLL. Perhaps its just not compatible with Apache 2? -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 3:50 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) On Tue, 14 Jan 2003, neal wrote: Date: Tue, 14 Jan 2003 15:38:55 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: WARP (Apache-Tomcat) This is totally screwey! Does WARP work on Windows or not?!?! My understanding is not. Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: WARP (Apache-Tomcat)
For anyone interested I just confirmed via a book I bought from Borders that WARP does not support Load balancing. So, for the archives ... WARP (Via the WebApp module) does not support: 1. Load balancing 2. Apache 2.0 (at least with Windows) And contrary to the Apache's own WebApp module site, Windows *IS* supported for 1.3.27 usage ... and its downloadable from the site. Man, Apache should really update this documentation ... I just waisted the majorty of a day figuring this stuff out (anyone from apache listening out there??). ;-) -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 7:58 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Well, I re-installed an older version of Apache (1.3.27) and WARP via mod_webApp seems to work fine nowand that was on Windows! So, I guess the compatability issue was with Apache 2.0. Hmm. That sucks. By the way, it was mentioned on this thread that mod_jk supports load balancing. Is that to say that WARP won't work in a multiple-host scenario?!?! :( Thanks Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 4:04 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) Really?!?! But I downloaded it from the win32 archives on the apache site (http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/v4.0.1/bin/win 32/). It even came with the libapr.dll - the library file compile as a windows DLL. Perhaps its just not compatible with Apache 2? -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 3:50 PM To: Tomcat Users List Subject: RE: WARP (Apache-Tomcat) On Tue, 14 Jan 2003, neal wrote: Date: Tue, 14 Jan 2003 15:38:55 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: WARP (Apache-Tomcat) This is totally screwey! Does WARP work on Windows or not?!?! My understanding is not. Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Actually, I always thought this was a requirement anyway. I mean it makes perfect sense that you have an index.html or index.jsp as a default page for any given directory ... including the root directory. So, I would actually expect that sort of behavior. I think you're right - this is how most other web servers currently work. As for breaking existing applications, i see your point but at least there's a solution there ... to place the welcome file into the correct directory position. Otherwise, there is no solution to the redirect problem. -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 11:52 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, neal wrote: Date: Wed, 8 Jan 2003 23:38:13 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat In you previous email you say: This still screws up relative references for people that use wierd welcome file paths like 'foo/bar.html', but will work for the majority. What do you mean by wierd welcome file paths. Consider the following entry in a web.xml file: welcome-file-list welcome-filefoo/bar.html/welcome-file /welcome-file-list If we change Tomcat to forwarding to the welcome file, relative references in the bar.html page will still be broken (because they are resolved by the browser, not the server). For the typical case: welcome-file-list welcome-fileindex.html/welcome-file /welcome-file-list The proposed solution (if there's no trailing slash, redirect to the original URL + /, otherwise forward) will work, and this is by far the most common case -- but the change is still going to break existing applications for some existing users. Will most relative paths still work? Is this the same sort of relative file path issues I would see if I forwarded (rather than redirect) from one JSP to another? If so, wouldn't this only be an issue if the welcome file was located somewhere other than the root of the application? Nothing in this discussion about welcome files has *any* impact on the way that relative URLs work in non-welcome pages. Even if we change the behavior of welcome files, they will continue to work the way they work today. The key to understanding what's going on is the following: * It is the *browser* that resolves relative URIs, not the server. * The *browser* resolves relative URIs against the URL showing in the location bar (unless you use a base element, which is pretty unusual). * A redirect changes the URL showing in the location bar, but a forward does not. The current behavior (redirect always) was done because, for Tomcat 3.0 and 3.1 (which did forwarding instead), a very FAQ question on TOMCAT-USER was why can't I use a relative URI in my welcome pages. This problem, of course, went away when we switched to redirect always, and has been the way that Tomcat has worked for the last several years. Given that users are going to complain no matter what the behavior is, the right answer is to find a balance that works the best for the most. The proposed solution (redirect to a URL with a trailing slash, or forward if there already is one) seems like a good candidate to meet that goal. By the way, Tomcat gets 80,000-120,000 downloads every single month (bigger numbers in the months when there are big new releases). I guess there are at least a few people in the world who think Tomcat is still commercially viable, in spite of what you consider a fatal flaw :-). Guess I won't be trusting *your* judgement on which server to use for my next application. :-) Neal Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 11:24 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, neal wrote: Date: Wed, 8 Jan 2003 23:11:44 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat So, in this scenario .. if a url without a directory is given and without a trailign slash, the redirect would not occur? That would fix this issue. I could certainly get behind that. :) You will change that opinion as soon as you realize that relative URIs in your welcome pages do not work any more :-). if the final element of the path is a directory (or a context) without a trailing slash, redirect to the same path with a trailing slash. But if the path is given with a trailing slash, forward to the welcome file. This is the right answer, IMHO. It also includes the use case where you just say: http://www.mycompany.com which is (essentially) a request for the welcome file of the top-level directory
RE: RewriteRules and Standalone Tomcat
Its *not* that simple. Pagerank (guaging inbound links from other sites) would need to all be coordinated to point to that specifc file. This would be very difficult. PR is the most significant factor in SERPs on most modern engines and if a good inbound link was to point to your base URL (which most will do) its not going to count when the engine realizes it is a 302. :( -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:42 AM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Me too. Especially if the solution is sooo simple: Just submit the url with the path to the welcome file to the searchenengines and most of them will be happy with that. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 11:32 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat I would disagree 100%. You're assuming that priority one for any commercial use of Tomcat is maximizing search engine placement for a given URL. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
I'm not presuming its priority #1 always, but yes I am presuming it is a very high priority ... but ... 80% of web traffic comes from search engines. Unless you're one you've got a major print and media advertising budget how else do you drive traffic? I suppose there are other possible scenarios such as Intranets or B2B apps, but I would suspect SEO is a significant factor for most who would deploy a commercial web application. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:32 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat I would disagree 100%. You're assuming that priority one for any commercial use of Tomcat is maximizing search engine placement for a given URL. I would be surprised if, out of all the people using Tomcat in a commercial situation, that was priority one for more than .1% or so. We're selling our applications like crazy, which use Tomcat, but then again, we use Apache as a rule for things on port 80. As far as we're concerned, Tomcat is perfect. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:18 AM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Well, a few things come to mind. 1. A comparison was made - using tomcat as a web server is like racing a mac truck. Well, for someone new to tomcat and apache (I just arrived from microsoft/iis land) the correct usage pattern was less than obvious ... I just knew that most people used tomcat/apache. I could have never anticipated this sort of issue. If this sort of issue is defended by the community (302s etc) then there should be a blatant disclaimer when downloading the standalone that it is not intended for production use. 2. As to teh chicken and egg analogy - that's a good point - does theory or an unfortunate reality dictate the direction of the product? I guess I would defer to point #1. If the product is not going to address the very real issues of production use, it should make it clear to users that it is not indended for production use. Granted the ideal is to sluff off such petty and rediculous issues put forth by the search engine defenses, but at the end of that argument the issue still exists as does the sobering fact that this will be a significant problem for anyone who chooses to deploy a commercial application using the product. neal --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat
You're comparing apples and oranges .. and pears (staying with the analogies ;-)). A high profile site of course does not need the engines to the same extent as a small site. Additionally, a small site with a mature link base (100s or 1000s of grade A links) will not recieve as much traffic from them either. For a new site (first year or so) its just the opposite. Besides, I was including places like Yahoo!, AOL, when I refer to search engine. Granted these are CPCs (fake search engines) but nonetheless google probably has 80% of the search engine market ... as for the 80% of traffic coming from search engines - its a statistic I recently read in a book. I can look it up for you if interested. If sounds though like the truth of this statistic has a lot to do with whether you're comparing apples ... oranges ... or pears. As for switching to Apache with 1hr work ... I'm also bucking that just because (a) my ISP will want to get involved and charge me hourly for the setup of an addt'l app and (b) I will have to get another $300 SSL cert from Trawte if I go that road. Sigh. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 5:34 AM To: 'Tomcat Users List' Subject: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat I'd love to see a cite for 80% of web traffic comes from search engines. I've worked on plenty of high-traffic public websites in my day, and have never, ever found that to be the case. If anything, more traffic comes from portals such as Yahoo, AOL, and MSN than anywhere else, and by that I mean direct links from the main page, which cost money. People don't get to nike.com by typing shoes in a search engine. Shoes on Google gets Vegetarian Shoes as the first link. Yeah, that's relevant. In my experience, search engine placement as a priority is the technique used by sites that don't have any money and want traffic for free. Keep in mind that traffic != sales, and traffic != revenue. They're not even directly proportional. How you drive traffic depends on the target audience. Sometimes its a search engine, I would say search engines are the last place people look when they want to spend money. Search engines are used, in my opinion, by people looking for information or anything else that's free, not for someplace to spend money. CDs at Google doesn't get me Amazon, yet that's the first place I go when I want to buy a CD from a major artist. Even a specific artist like Eminem CD doesn't get me Amazon anywhere near the top of the results. For us, our Tomcat-based commercial applications are sold face-to-face by salespeople. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 6:54 AM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat I'm not presuming its priority #1 always, but yes I am presuming it is a very high priority ... but ... 80% of web traffic comes from search engines. Unless you're one you've got a major print and media advertising budget how else do you drive traffic? I suppose there are other possible scenarios such as Intranets or B2B apps, but I would suspect SEO is a significant factor for most who would deploy a commercial web application. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat
Oh C'mon! How?!?!?! Telepathy? ;-) I know that there are other means such as word of mouth and as Craig said there's probably not a way to verify these numbers anyway ... besides I'm just quoting what I read. But whether you agree with the 80% number or not I would think surely the outrageous fees charged by competent SEOs is proof enough of their significance. On the Google lists I participate in, its commonly acknowledged that getting dropped from Google can break the back of many internet businesses. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 11:17 AM To: 'Tomcat Users List' Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat If the site has real value, the customers will find it all by themselves. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 1:03 PM To: Tomcat Users List Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat You're comparing apples and oranges .. and pears (staying with the analogies ;-)). A high profile site of course does not need the engines to the same extent as a small site. Additionally, a small site with a mature link base (100s or 1000s of grade A links) will not recieve as much traffic from them either. For a new site (first year or so) its just the opposite. Besides, I was including places like Yahoo!, AOL, when I refer to search engine. Granted these are CPCs (fake search engines) but nonetheless google probably has 80% of the search engine market ... as for the 80% of traffic coming from search engines - its a statistic I recently read in a book. I can look it up for you if interested. If sounds though like the truth of this statistic has a lot to do with whether you're comparing apples ... oranges ... or pears. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat
Is that right? The key we generated for Tomcat will also work on Apache?!?! This is surpising (though a plesant suprise) because the method by which we had to create the key for tomcat was different than what the admin had apparently done prior with Apache. -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 11:43 AM To: Tomcat Users List Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat (a) my ISP will want to get involved and charge me hourly for the setup of an addt'l app This is hosted on their server, and they don't have apache installed? Who is the hosting service? (b) I will have to get another $300 SSL cert from Trawte Why? The domain name isn't changing, and both Apache and Tomcat use X.509 certs. What's the issue? --- Noel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat
Yes but its not that simple. So many factors would play into each individuals site's break down. If you don't focus on them, if you don't optimize for them, and if you have significant other sources of traffic of course that will throw off the thing ... particularly if you have relationships through these midlets. No doubt every site is different but search engines are still the yellow pages of the Internet and with the Internet verging on information overload, ppl are bound to rely even more on central directories are enginesparticularly for new and lesser known sites. If we are to truly contest these numbers we would have to look at sooo many different factors and a rather large cross-section. I hear what you're saying that it is entirely possible to be autonomous from the engines, but many people ... I would venture to say most are not! But I guess that's all speculation unless we care to undertake a dramatic new survey of Internet and search engine usage patterns. ;-) -Original Message- From: Jon Eaves [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:59 PM To: Tomcat Users List Subject: Re: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat Hiya Neal (and others) As a counterpoint to your argument about search engines and small sites I have some real numbers: From my website referrer stats: (For an Apache HTTP: http://www.eaves.org) Direct requests : 28% Google.com : 1.5% Google images : 0.7% search.yahoo.com : 0.3% Google.ca : 0.15% Google.co.uk : 0.15% Google.it : 0.11% Google.de : 0.09% Google.com.au : 0.08% Google.co.nz : 0.06% Google.fr : 0.03% Google.pl : 0.03% Google.nl : 0.03% altavista.com : 0.03% au.altavista.com : 0.02% The rest of the traffic is from a whole load of Java MIDlet portals. Total search engines combined: ~4% Now, I'm not running java.sun.com or anything like that but for a personal website I get an average of 30,000 hits a month, and I suspect that the only way that people find my site would be: 1. Signature links in email 2. Search engines It's not like anybody is going to be trying to guess my URL just to see what is there ;-) And the best thing is that I have a site that is just running Tomcat, on a wacky URL to compare this against: (Tomcat: http://www.eaves.org:28080/) Direct requests : 55% looksmart.com : 15% eaves.org : 9% google : 6% search.msn.com : 5% yahoo.com : 1% google.ca : 1% Now, I don't trust these numbers as much because the hits are so much lower 2000 hits a month, but it's clear in my case that there is no, or little penalty for whatever behaviour Tomcat might have. Of course, YMMV, batteries not includes, offer void where prohibited by law. Cheers, -- jon neal wrote: You're comparing apples and oranges .. and pears (staying with the analogies ;-)). A high profile site of course does not need the engines to the same extent as a small site. Additionally, a small site with a mature link base (100s or 1000s of grade A links) will not recieve as much traffic from them either. For a new site (first year or so) its just the opposite. Besides, I was including places like Yahoo!, AOL, when I refer to search engine. Granted these are CPCs (fake search engines) but nonetheless google probably has 80% of the search engine market ... as for the 80% of traffic coming from search engines - its a statistic I recently read in a book. I can look it up for you if interested. If sounds though like the truth of this statistic has a lot to do with whether you're comparing apples ... oranges ... or pears. As for switching to Apache with 1hr work ... I'm also bucking that just because (a) my ISP will want to get involved and charge me hourly for the setup of an addt'l app and (b) I will have to get another $300 SSL cert from Trawte if I go that road. Sigh. Neal -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
What you're talking about is repeat business .. I'm talking about getting the introductions in the first place. Well, aside from the discussion of the importance of SEs in a business model, I think most would agree it is a commonly used tool - independent of ideals. I'm going to look more into Apache and I will also take a look at the patch that apparently exists for working around the 302 that someone else wrote. Thanks for the tips. As for the future of Tomcat in this regard, I personally would love to see the 302 thing go away. It will be interesting to see which direction is taken. Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 12:10 PM To: 'Tomcat Users List' Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat I can only comment on my own experience. I'm assuming that the application wants to earn revenue, and not do so from advertising (ad-only models rarely work). That means sales. I've been purchasing on the net since 1996. Unless the site has a product that no one else on earth and no other site has, the true differentiator (and driver) of success in the long term will be dollar value, user experience, and customer support, not search engine placement. In that scenario, good placement on sites like epinions.com and resellerratings.com, etc. from regular customers is much more valuable. Let's face it, just about any product being sold nowadays, including software, is a commodity item. If it's a high ticket item, then chances are a face-to-face (or several) will be required to get a check, which makes search engine placement just about irrelevant, as a good salesperson working on 100% commission (the good ones always work on 100% commission) will have no problem developing their own leads. If it were me, and I was designing a business model, the last place I would be spending time and resources would be search engine placement, or gyrating an application to enhance search engine placement. ;) But that's me. The search engine placement lists and groups are very similar to the get more traffic lists and groups. I've lurked on both over the years, and I could never get past the idea that in just about every case, it's pretty much just endless discussions about churn. Generic traffic is just the same set of eyeballs over and over, and the traffic brokers you run into will NEVER back up their claims with sales conversion numbers, because they know full well that there is no relationship between the number of people visiting a site and the total amount of sales. They'll claim 10,000 unique visitors to your site this week guaranteed!! but that has no bearing whatsoever on sales. I'd rather focus on making my customers stunned by the value and good customer service I provide. I'll get lots more sales that way over time. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 2:26 PM To: Tomcat Users List Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat Oh C'mon! How?!?!?! Telepathy? ;-) I know that there are other means such as word of mouth and as Craig said there's probably not a way to verify these numbers anyway ... besides I'm just quoting what I read. But whether you agree with the 80% number or not I would think surely the outrageous fees charged by competent SEOs is proof enough of their significance. On the Google lists I participate in, its commonly acknowledged that getting dropped from Google can break the back of many internet businesses. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 11:17 AM To: 'Tomcat Users List' Subject: RE: [OFF-TOPIC] RE: RewriteRules and Standalone Tomcat If the site has real value, the customers will find it all by themselves. John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RewriteRules and Standalone Tomcat
What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Oh. :( But this was actually a solution offered specific to a Tomcat issue: Issue: Unlike Apache, tomcat automatically redirects to the welcome page, rather than forwarding. In other words, to present the welcome page tomcat will literally redirect (http 302) to www.xyz.com/index.html, rather than staying at www.xyz.com. I do not want this effect as I am affraid it will have negative effects on my search engine placement. I was given the advice to use a RewriteRule to fix this problem. If this is not the solution, does anyone know what the solution is? I was told this is actually a feature of tomcat ... I call it a PAIN IN THE ASS, and a serious oversight for standalone Tomcat. Anyone know a solution? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:16 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Beat me with a stick if I'm wrong, but RewriteRule is for Apache when using mod_rewrite, I don't think you can use it in server.xml or web.xml. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 AM To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
That would explain why I found references to RewriteRules for Apache on the Internet, but none for Tomcat. Damn! -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:16 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Beat me with a stick if I'm wrong, but RewriteRule is for Apache when using mod_rewrite, I don't think you can use it in server.xml or web.xml. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 AM To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Oh, does that mean it *is* possible to use RewriteRules with Tomcat Standalone then? :-\ Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 1:04 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Yes, specific to a Tomcat issue, but the solution incorporates Apache. :) John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:54 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Oh. :( But this was actually a solution offered specific to a Tomcat issue: Issue: Unlike Apache, tomcat automatically redirects to the welcome page, rather than forwarding. In other words, to present the welcome page tomcat will literally redirect (http 302) to www.xyz.com/index.html, rather than staying at www.xyz.com. I do not want this effect as I am affraid it will have negative effects on my search engine placement. I was given the advice to use a RewriteRule to fix this problem. If this is not the solution, does anyone know what the solution is? I was told this is actually a feature of tomcat ... I call it a PAIN IN THE ASS, and a serious oversight for standalone Tomcat. Anyone know a solution? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:16 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Beat me with a stick if I'm wrong, but RewriteRule is for Apache when using mod_rewrite, I don't think you can use it in server.xml or web.xml. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 AM To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
It sounds like you are saying that you must also run Apache ... that Tomcat alone is not sufficient. Is this correct? And that I would setup mod_rewrite within Apache before it gets to Tomcat? Wouldn't this then mean that you're not actually using Apache as a Standalone? Are you connecting to Tomcat via WARP? I'm confused. :( -Original Message- From: Gary Gwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:35 PM To: Tomcat Users List Subject: Re: RewriteRules and Standalone Tomcat Yes, but your requests must be passed through Apache to Tomcat-Standalone via mod_jk. We do this on our site and it works nicely. The URL requests are processed by mod_rewrite before mod_jk forwards them to Tomcat, so the Apache behavior you desired is achieved. I don't think that Tomcat-Standalone means what it looks like it should mean, if you know what I mean ;-) Gary neal wrote: Oh, does that mean it *is* possible to use RewriteRules with Tomcat Standalone then? :-\ Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 1:04 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Yes, specific to a Tomcat issue, but the solution incorporates Apache. :) John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:54 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Oh. :( But this was actually a solution offered specific to a Tomcat issue: Issue: Unlike Apache, tomcat automatically redirects to the welcome page, rather than forwarding. In other words, to present the welcome page tomcat will literally redirect (http 302) to www.xyz.com/index.html, rather than staying at www.xyz.com. I do not want this effect as I am affraid it will have negative effects on my search engine placement. I was given the advice to use a RewriteRule to fix this problem. If this is not the solution, does anyone know what the solution is? I was told this is actually a feature of tomcat ... I call it a PAIN IN THE ASS, and a serious oversight for standalone Tomcat. Anyone know a solution? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:16 AM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Beat me with a stick if I'm wrong, but RewriteRule is for Apache when using mod_rewrite, I don't think you can use it in server.xml or web.xml. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 AM To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Gary Gwin http://www.cafesoft.com * * * * The Cafesoft Access Management System, Cams, is security* * software that provides single sign-on authentication and* * centralized access control for Apache, Tomcat, and custom * * resources. * * * * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat version 4
John, You say there is a patch for Tomcat that will fix this redirect thing ... or at least allow me to configure it to not redirect like this? Great! Do you know specifically which patch this is? Is there any documentation that you know of regarding the patches ability to tweak this behavior? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:37 PM To: 'Tomcat Users List' Subject: RE: Tomcat version 4 Check the Tomcat log files, in CATALINA_HOME/logs. Typically, you'll want the file that has a name of the form: hostname_log.-MM-DD.txt Provided the logger defaults haven't been changed. You can also look for files stdout.log and stderr.log for messages from Tomcat itself (like startup confirmation, etc). John -Original Message- From: Reis, Tom [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 5:32 PM To: Tomcat Users List (E-mail) Subject: Tomcat version 4 Is there a way to record errors I am getting on the Dos screen? After I start up Tomcat and I try to run a servlet I receive a list of errors on the Tomcat Dos screen and I need to save these to send them to our programmer. Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
John, You say there is a patch for Tomcat that will fix this redirect thing ... or at least allow me to configure it to not redirect like this? Great! Do you know specifically which patch this is? Is there any documentation that you know of regarding the patches ability to tweak this behavior? BTW - I'm currently using Tomcat 4.0.4. I wouldn't by chance already have this ability would I? I didn't see anything in the docs. Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:25 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Many people do not run Tomcat on port 80. Some do. Those who don't, run Apache on port 80 and use a connector to pass requests to Tomcat. Tomcat Stand-alone means Tomcat running on port 80, or some other port with the port number appended to the request. That is, no Apache in the mix. The suggestion to use RewriteRule only works if you use mod_rewrite, which is an Apache module. This means that Tomcat no longer listens on port 80, but on another port such as 8009, and communicates with Apache via that port. Apache listens on port 80, and in the case of the proposed solution, mod_rewrite would process the URL prior to the Tomcat connector (mod_jk or mod_jk2) getting it, which would avoid the 302 from Tomcat you are concerned about, since Tomcat would see it as a normal request, not a request that needed to be redirected or forwarded to the default welcome page. RewriteRule cannot be used in Tomcat by itself. Not in server.xml, not in web.xml. It is a mod_rewrite directive, and mod_rewrite is an Apache module. If you want to use RewriteRule and mod_rewrite, install Apache, setup mod_rewrite, setup a connector, disable the CoyoteConnector on port 80 (and 8080 if it is still enabled) in server.xml, make sure there is a CoyoteConnector listening on port 8009 (or some other port for JK/JK2) in Tomcat's server.xml, and call it good. If you do not want to use Apache in any way shape or form, then wait for or apply the patch pointed out by Tim earlier in the thread. Judging from what I read in that thread, there are very good reasons for the 302, though I didn't pursue the thread far enough back to get an idea of exactly what they are. In any case, with the patch, the existing behavior (302) is the default, and you will have to specifically configure Tomcat to behave differently. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 5:47 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat It sounds like you are saying that you must also run Apache ... that Tomcat alone is not sufficient. Is this correct? And that I would setup mod_rewrite within Apache before it gets to Tomcat? Wouldn't this then mean that you're not actually using Apache as a Standalone? Are you connecting to Tomcat via WARP? I'm confused. :( -Original Message- From: Gary Gwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:35 PM To: Tomcat Users List Subject: Re: RewriteRules and Standalone Tomcat Yes, but your requests must be passed through Apache to Tomcat-Standalone via mod_jk. We do this on our site and it works nicely. The URL requests are processed by mod_rewrite before mod_jk forwards them to Tomcat, so the Apache behavior you desired is achieved. I don't think that Tomcat-Standalone means what it looks like it should mean, if you know what I mean ;-) Gary neal wrote: Oh, does that mean it *is* possible to use RewriteRules with Tomcat Standalone then? :-\ Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 1:04 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Yes, specific to a Tomcat issue, but the solution incorporates Apache. :) John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:54 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Oh. :( But this was actually a solution offered specific to a Tomcat issue: Issue: Unlike Apache, tomcat automatically redirects to the welcome page, rather than forwarding. In other words, to present the welcome page tomcat will literally redirect (http 302) to www.xyz.com/index.html, rather than staying at www.xyz.com. I do not want this effect as I am affraid it will have negative effects on my search engine placement. I was given the advice to use a RewriteRule to fix this problem. If this is not the solution, does anyone know what the solution is? I was told this is actually a feature of tomcat ... I call it a PAIN IN THE ASS, and a serious oversight for standalone Tomcat. Anyone know a solution? Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:16 AM To: 'Tomcat Users List' Subject: RE
RE: RewriteRules and Standalone Tomcat
John, Thanks for the threads. I will certainly read them. I can't imagine why Tomcat wouldn't support this behavior unless there is another issue in Tomcat that this is covering up ... I mean this is basic http server stuff, I thought. All the same...thanks! :) Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:51 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat See Tim Moore's reply to your post earlier today: http://marc.theaimsgroup.com/?l=tomcat-userm=104206237029628w=2 The discussion on the tomcat-dev list is here: http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg38868.html My point was that as you can see in the tomcat-dev discussion, Remy says I will -1 this patch unless the behavior is made optional which means there is a reason that Tomcat does the 302 and he feels strongly enough about it to register a negative vote for changing that behavior. You might want to research why that is before you decide to change it, as changing that behavior might affect something else that is more important to you than search engine placement. In any case, you can apply the patch yourself, but to do that, you will need to build Tomcat (or at least the affected parts) from source. Or wait until the next release. My guess is you will have to move up to 4.1.18 to apply the patch, though I don't have a good feel for the differences in the different versions. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:45 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat John, You say there is a patch for Tomcat that will fix this redirect thing ... or at least allow me to configure it to not redirect like this? Great! Do you know specifically which patch this is? Is there any documentation that you know of regarding the patches ability to tweak this behavior? BTW - I'm currently using Tomcat 4.0.4. I wouldn't by chance already have this ability would I? I didn't see anything in the docs. Thanks. Neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 3:25 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Many people do not run Tomcat on port 80. Some do. Those who don't, run Apache on port 80 and use a connector to pass requests to Tomcat. Tomcat Stand-alone means Tomcat running on port 80, or some other port with the port number appended to the request. That is, no Apache in the mix. The suggestion to use RewriteRule only works if you use mod_rewrite, which is an Apache module. This means that Tomcat no longer listens on port 80, but on another port such as 8009, and communicates with Apache via that port. Apache listens on port 80, and in the case of the proposed solution, mod_rewrite would process the URL prior to the Tomcat connector (mod_jk or mod_jk2) getting it, which would avoid the 302 from Tomcat you are concerned about, since Tomcat would see it as a normal request, not a request that needed to be redirected or forwarded to the default welcome page. RewriteRule cannot be used in Tomcat by itself. Not in server.xml, not in web.xml. It is a mod_rewrite directive, and mod_rewrite is an Apache module. If you want to use RewriteRule and mod_rewrite, install Apache, setup mod_rewrite, setup a connector, disable the CoyoteConnector on port 80 (and 8080 if it is still enabled) in server.xml, make sure there is a CoyoteConnector listening on port 8009 (or some other port for JK/JK2) in Tomcat's server.xml, and call it good. If you do not want to use Apache in any way shape or form, then wait for or apply the patch pointed out by Tim earlier in the thread. Judging from what I read in that thread, there are very good reasons for the 302, though I didn't pursue the thread far enough back to get an idea of exactly what they are. In any case, with the patch, the existing behavior (302) is the default, and you will have to specifically configure Tomcat to behave differently. John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 5:47 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat It sounds like you are saying that you must also run Apache ... that Tomcat alone is not sufficient. Is this correct? And that I would setup mod_rewrite within Apache before it gets to Tomcat? Wouldn't this then mean that you're not actually using Apache as a Standalone? Are you connecting to Tomcat via WARP? I'm confused. :( -Original Message- From: Gary Gwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:35 PM To: Tomcat Users List Subject: Re: RewriteRules and Standalone Tomcat Yes, but your requests must be passed through Apache to Tomcat-Standalone via mod_jk. We do this on our site and it works nicely. The URL requests are processed
RE: RewriteRules and Standalone Tomcat
Hmm. But the fact still remains that Tomcat Standalone will not be a commercially viable http server on its own if it can't display a welcome page without redirecting to the page. Dispite all of Tomcat's other abilities, not having this ability is like shooting the standalone notion in the foot. Because of the search engine spidering implications of starting off with a 302 redirect, a Tomcat-standalone-hosted website will likley never place well in most major search engines. So aside from theory ... this is not a good feature, certainly not a viable one. :( Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:07 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 20:33:50 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat No problem, glad to help. Remember, Tomcat is not a HTTP server. It supports HTTP as a matter of convenience. You can run Tomcat all day long without a HTTP or HTTPS connector, and as far as I know, there is nothing in the spec that says Tomcat has to meet certain requirements for HTTP or HTTPS. CoyoteConnector is HTTP/1.1 compliant, but again, that's more for convenience and compatibility than a design requirement. Auoting from Servlet Specification, Version 2.3, Section 1.2: All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response based protocols (such as HTTPS (HTTP over SSL) may be supported. The minimum required version of the HTTP specification that a container must implement is HTTP/1.0. It is strongly suggested that containers implement the HTTP/1.1 specification as well. So, a servlet container (which is either Tomcat standalone or Tomcat+Apache) *must* support HTTP. I'm sure the folks on tomcat-dev could shed some more light on it. Of course, this statement does nothing to resolve the issue of what the right welcome file behavior is -- the HTTP spec is silent about that :-). John Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Noel, Yes that was you that gave me this solution. But know ... it was actually in the context of finding a way around this very problem which I brought up a while back. I guess the detail that I was using tomcat standalone was not understood. I appreciate the solution but yeah ... now that I'm finally getting around to putting it into action, I realized the problem. Neal -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:34 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Neal, I told you that solution in the context of your avoiding a redirect (302), not in the context of standalone Tomcat. mod_rewrite is an Apache module. http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg38750.html is the start of a thread on patching Tomcat to do a forward instead of a redirect. Matt Parker's latest patch (not the one in the message) was approved, so long as he keeps the default to the current behavior for now. For Tomcat 5, Remy Maucherat plans to include this functionality in the mapper. --- Noel P.S. If someone needs something from me, direct e-mail might be useful if I don't reply to the list promptly. I'm swamped, and sometimes don't have time to get to the tomcat-user folder. This was my first (and probably only) pass today, and I only checked this thread because RewriteRules is one of my fun topics. -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:51 To: Tomcat Users List Subject: RewriteRules and Standalone Tomcat What exaclty is a RewriteRule and how is it used with Standalone Tomcat? Do I define my RewriteRules somewhere in server.xml or web.xml? A couple of months ago, Noel told me how I could get Tomcat to show the content of the default welcome page without redirecting (http 302) to the file, using a RewriteRule. I took notes from that email and set it aside only to realize when I returned ... that I have no idea what to do with this info! And of course no info is available (that I could find) online or in the Tomcat manual explaining this. :( Could someone please explain how this RewriteRule would be integrated into Tomcat: RewriteRule ^/$ /index.html [L] Thanks! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
So, in this scenario .. if a url without a directory is given and without a trailign slash, the redirect would not occur? That would fix this issue. I could certainly get behind that. :) if the final element of the path is a directory (or a context) without a trailing slash, redirect to the same path with a trailing slash. But if the path is given with a trailing slash, forward to the welcome file. -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:36 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 22:19:47 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat OK, so what's the rationalization for the 302? Can you shed some light on that? Consider a typical welcome page that includes: body ... img src=logo.jpg ... /body For a context path /myapp, consider what happens when I type http://www.mycompany.com/myapp; in to the browser. With a forward, the relative reference to logo.jpg gets resolved wrong (from the user's perspective) because it's the *browser* that resolves it. Want proof? Go back about three years when Tomcat 3.0 and 3.1 behaved this way, and why don't images in a welcome page work was a FAQ on TOMCAT-USER :-). Changing to the current behavior was the result of a bug report about this, that had widespread support from the user community at the time. Assuming that we can be compatible with the servlet spec language (for 2.4, that means convince the EG to clarify it this way), I think the right answer is the one proposed in the TOMCAT-DEV discussion -- if the final element of the path is a directory (or a context) without a trailing slash, redirect to the same path with a trailing slash. But if the path is given with a trailing slash, forward to the welcome file. This still screws up relative references for people that use wierd welcome file paths like foo/bar.html, but will work for the majority -- and it seems to be the way that Apache and other web servers deal with the issue. John Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 9:07 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 20:33:50 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat No problem, glad to help. Remember, Tomcat is not a HTTP server. It supports HTTP as a matter of convenience. You can run Tomcat all day long without a HTTP or HTTPS connector, and as far as I know, there is nothing in the spec that says Tomcat has to meet certain requirements for HTTP or HTTPS. CoyoteConnector is HTTP/1.1 compliant, but again, that's more for convenience and compatibility than a design requirement. Auoting from Servlet Specification, Version 2.3, Section 1.2: All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response based protocols (such as HTTPS (HTTP over SSL) may be supported. The minimum required version of the HTTP specification that a container must implement is HTTP/1.0. It is strongly suggested that containers implement the HTTP/1.1 specification as well. So, a servlet container (which is either Tomcat standalone or Tomcat+Apache) *must* support HTTP. I'm sure the folks on tomcat-dev could shed some more light on it. Of course, this statement does nothing to resolve the issue of what the right welcome file behavior is -- the HTTP spec is silent about that :-). John Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RewriteRules and Standalone Tomcat
Well, a few things come to mind. 1. A comparison was made - using tomcat as a web server is like racing a mac truck. Well, for someone new to tomcat and apache (I just arrived from microsoft/iis land) the correct usage pattern was less than obvious ... I just knew that most people used tomcat/apache. I could have never anticipated this sort of issue. If this sort of issue is defended by the community (302s etc) then there should be a blatant disclaimer when downloading the standalone that it is not intended for production use. 2. As to teh chicken and egg analogy - that's a good point - does theory or an unfortunate reality dictate the direction of the product? I guess I would defer to point #1. If the product is not going to address the very real issues of production use, it should make it clear to users that it is not indended for production use. Granted the ideal is to sluff off such petty and rediculous issues put forth by the search engine defenses, but at the end of that argument the issue still exists as does the sobering fact that this will be a significant problem for anyone who chooses to deploy a commercial application using the product. neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:27 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Sounds like the makings of a good debate, and a classic chicken and egg problem. Does Tomcat submit to how some search engines work, even if there are reasons not to do so, or do search engines accept 302 behavior? Do ALL search engines disregard 302s? Think about it...search engines probably disregard 302s because of abusive behavior in the past from a minority of web site owners. Should that dictate the design of a major software application? John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 9:29 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Hmm. But the fact still remains that Tomcat Standalone will not be a commercially viable http server on its own if it can't display a welcome page without redirecting to the page. Dispite all of Tomcat's other abilities, not having this ability is like shooting the standalone notion in the foot. Because of the search engine spidering implications of starting off with a 302 redirect, a Tomcat-standalone-hosted website will likley never place well in most major search engines. So aside from theory ... this is not a good feature, certainly not a viable one. :( Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:07 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 20:33:50 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat No problem, glad to help. Remember, Tomcat is not a HTTP server. It supports HTTP as a matter of convenience. You can run Tomcat all day long without a HTTP or HTTPS connector, and as far as I know, there is nothing in the spec that says Tomcat has to meet certain requirements for HTTP or HTTPS. CoyoteConnector is HTTP/1.1 compliant, but again, that's more for convenience and compatibility than a design requirement. Auoting from Servlet Specification, Version 2.3, Section 1.2: All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response based protocols (such as HTTPS (HTTP over SSL) may be supported. The minimum required version of the HTTP specification that a container must implement is HTTP/1.0. It is strongly suggested that containers implement the HTTP/1.1 specification as well. So, a servlet container (which is either Tomcat standalone or Tomcat+Apache) *must* support HTTP. I'm sure the folks on tomcat-dev could shed some more light on it. Of course, this statement does nothing to resolve the issue of what the right welcome file behavior is -- the HTTP spec is silent about that :-). John Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
RE: RewriteRules and Standalone Tomcat
Just one more thought on the matter, for me tonight: I've deployed an app using Tomcat Standalone (www.hotel.us) and while there have been several issues that were a little less than obvious, I have found a solution to every single one of them and am overall pretty satisfied with tomcat. but this one little thing would force me to have to go to apache. IMHO, it would be a shame to not be able to use the product for this one little reason. Neal -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 11:18 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Well, a few things come to mind. 1. A comparison was made - using tomcat as a web server is like racing a mac truck. Well, for someone new to tomcat and apache (I just arrived from microsoft/iis land) the correct usage pattern was less than obvious ... I just knew that most people used tomcat/apache. I could have never anticipated this sort of issue. If this sort of issue is defended by the community (302s etc) then there should be a blatant disclaimer when downloading the standalone that it is not intended for production use. 2. As to teh chicken and egg analogy - that's a good point - does theory or an unfortunate reality dictate the direction of the product? I guess I would defer to point #1. If the product is not going to address the very real issues of production use, it should make it clear to users that it is not indended for production use. Granted the ideal is to sluff off such petty and rediculous issues put forth by the search engine defenses, but at the end of that argument the issue still exists as does the sobering fact that this will be a significant problem for anyone who chooses to deploy a commercial application using the product. neal -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:27 PM To: 'Tomcat Users List' Subject: RE: RewriteRules and Standalone Tomcat Sounds like the makings of a good debate, and a classic chicken and egg problem. Does Tomcat submit to how some search engines work, even if there are reasons not to do so, or do search engines accept 302 behavior? Do ALL search engines disregard 302s? Think about it...search engines probably disregard 302s because of abusive behavior in the past from a minority of web site owners. Should that dictate the design of a major software application? John -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 9:29 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat Hmm. But the fact still remains that Tomcat Standalone will not be a commercially viable http server on its own if it can't display a welcome page without redirecting to the page. Dispite all of Tomcat's other abilities, not having this ability is like shooting the standalone notion in the foot. Because of the search engine spidering implications of starting off with a 302 redirect, a Tomcat-standalone-hosted website will likley never place well in most major search engines. So aside from theory ... this is not a good feature, certainly not a viable one. :( Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 6:07 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 20:33:50 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat No problem, glad to help. Remember, Tomcat is not a HTTP server. It supports HTTP as a matter of convenience. You can run Tomcat all day long without a HTTP or HTTPS connector, and as far as I know, there is nothing in the spec that says Tomcat has to meet certain requirements for HTTP or HTTPS. CoyoteConnector is HTTP/1.1 compliant, but again, that's more for convenience and compatibility than a design requirement. Auoting from Servlet Specification, Version 2.3, Section 1.2: All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response based protocols (such as HTTPS (HTTP over SSL) may be supported. The minimum required version of the HTTP specification that a container must implement is HTTP/1.0. It is strongly suggested that containers implement the HTTP/1.1 specification as well. So, a servlet container (which is either Tomcat standalone or Tomcat+Apache) *must* support HTTP. I'm sure the folks on tomcat-dev could shed some more light on it. Of course, this statement does nothing to resolve the issue of what the right welcome file behavior is -- the HTTP spec is silent about that :-). John Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL
RE: RewriteRules and Standalone Tomcat
In you previous email you say: This still screws up relative references for people that use wierd welcome file paths like 'foo/bar.html', but will work for the majority. What do you mean by wierd welcome file paths. Will most relative paths still work? Is this the same sort of relative file path issues I would see if I forwarded (rather than redirect) from one JSP to another? If so, wouldn't this only be an issue if the welcome file was located somewhere other than the root of the application? Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 11:24 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, neal wrote: Date: Wed, 8 Jan 2003 23:11:44 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat So, in this scenario .. if a url without a directory is given and without a trailign slash, the redirect would not occur? That would fix this issue. I could certainly get behind that. :) You will change that opinion as soon as you realize that relative URIs in your welcome pages do not work any more :-). if the final element of the path is a directory (or a context) without a trailing slash, redirect to the same path with a trailing slash. But if the path is given with a trailing slash, forward to the welcome file. This is the right answer, IMHO. It also includes the use case where you just say: http://www.mycompany.com which is (essentially) a request for the welcome file of the top-level directory of the ROOT webapp. This should be redirected to: http://www.mycompany.com/ just like Apache does it, and then forwarded to the welcome file from there, so that relative URIs still work as expected. Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:36 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 22:19:47 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat OK, so what's the rationalization for the 302? Can you shed some light on that? Consider a typical welcome page that includes: body ... img src=logo.jpg ... /body For a context path /myapp, consider what happens when I type http://www.mycompany.com/myapp; in to the browser. With a forward, the relative reference to logo.jpg gets resolved wrong (from the user's perspective) because it's the *browser* that resolves it. Want proof? Go back about three years when Tomcat 3.0 and 3.1 behaved this way, and why don't images in a welcome page work was a FAQ on TOMCAT-USER :-). Changing to the current behavior was the result of a bug report about this, that had widespread support from the user community at the time. Assuming that we can be compatible with the servlet spec language (for 2.4, that means convince the EG to clarify it this way), I think the right answer is the one proposed in the TOMCAT-DEV discussion -- if the final element of the path is a directory (or a context) without a trailing slash, redirect to the same path with a trailing slash. But if the path is given with a trailing slash, forward to the welcome file. This still screws up relative references for people that use wierd welcome file paths like foo/bar.html, but will work for the majority -- and it seems to be the way that Apache and other web servers deal with the issue. John Craig -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 9:07 PM To: Tomcat Users List Subject: RE: RewriteRules and Standalone Tomcat On Wed, 8 Jan 2003, Turner, John wrote: Date: Wed, 8 Jan 2003 20:33:50 -0500 From: Turner, John [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: RewriteRules and Standalone Tomcat No problem, glad to help. Remember, Tomcat is not a HTTP server. It supports HTTP as a matter of convenience. You can run Tomcat all day long without a HTTP or HTTPS connector, and as far as I know, there is nothing in the spec that says Tomcat has to meet certain requirements for HTTP or HTTPS. CoyoteConnector is HTTP/1.1 compliant, but again, that's more for convenience and compatibility than a design requirement. Auoting from Servlet Specification, Version 2.3, Section 1.2: All servlet containers must support HTTP as a protocol for requests and responses, but additional request/response based protocols (such as HTTPS (HTTP over SSL) may be supported
Tomcat - a search engine liability?!?!
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 .mdlx and servlets without extensions appear to be S.O.L as well. My guess is struts and similar other frameworks are in the same boat. I determined this by downloading the google toolbar and watching the page rank for various pages. Pages with a grayed out rank are not indexed. ASP, and JSP were the only dynamic extensions I consistantly saw that were being indexed. And now a question (and possible other detriment): 2. Tomcat standalone automatically redirects (http 302) to index.html or whatever default file is otherwise specified in the welcome pages node of the server.xml file. Potentially BIG problem! Search engines HATE 302s And, if a link is provided to http://www.xyz.com whereas, requesting that page from tomcat goes to http://www.xyz.com/index.html - the link is likley not included by most search engines, and this is huge for for anyone who realizes that inbound links is significant to search engine placement. But how does this get turned off? The only advice I've gotten is to write a servlet that parse these requests and appropriately forwards the request to the right file. But again, I refer to the problem listed above - servlets to NOT get indexed on the engine that handles 80% of search traffic. For anyone out there listening, any change this auto-redirect 'feature' might have an off feature in future revisions? Or, does anyone know of away around that redirect issue as of current? Thanks. Neal Cabage -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat - a search engine liability?!?!
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 in front of it, or is it easier to write one of these solutions? Also, jsut to clarify - these mappings filters and rewrites would all occur prior to initial output and result in a completely normal, well-formed server header for a requested document? I mean, http status code would be 200, the extention and content-type could appear to be html, etc? Would there be any clue to a search engine that any of these things aren't what they appear to be? Thanks. Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 7:10 PM To: Tomcat Users List Subject: RE: Tomcat - 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] Subject: RE: Tomcat - a search engine liability?!?! Colin, The difference is that servlet mapping doesn't allow regex replacement, whereas mod_rewrite allows: RewriteRule ^(.*)/mdlx/(.*).html$ $1/$2.mdlx That is completely off-the-cuff, so it might be syntactically wrong. If anyone here isn't familar with mod_rewrite, I highly recommend the URL Rewriting Guide: http://httpd.apache.org/docs-2.0/misc/rewriteguide.html. To paraphrase a famous slogan: mod_rewrite -- Don't Run Your Web Server Without It. 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 regexp replacement if you want :-). --- Noel Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat - a search engine liability?!?!
Thanks but the problem isn't with jsps, and actually, mapping to another extension was more of a secondary problem. The primary problem becomes that I need Tomcat to not redirect (http 302) to a different URL, I want it to stay at http://www.xyz.com and simply show the contents of the default page rather than redirect ... a behavior seen in every other http server. The servlets issue was mentioned (a) to let everyone know that they don't index and (b) to say that using a servlet mapped to / that would simply forward to correct default file won't work because servlets don't index. So, I'm guessing this filter thing is something to look at, mod_rewrite too. I'm also going to take a look at apache - my big hesitation there is that the SSL certificate is already bound to Tomcat ... I think I'd have to buy another to work with Apache. 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, 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 in front of it, or is it easier to write one of these solutions? Don't throw in that towel yet! Here's one easy solution: Configure Tomcat so that .htm pages are handled as jsps. This is easy to do: Modify the web.xml (for the server, not the application itself) so that the jsp servlet handles .htm files. Also .htm should be taken out of the mime types of web.xml in that same file. Obviously, be very careful that all your static html files are .html if you do this. One advantage of this is that it means that your server isn't advertising what kind of back-end technology it is using. Less information is often better. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat - a search engine liability?!?!
Oh wow ... very cool. Thanks Joel. I'm going to dig into this and learn exactly what a rewrite rule is first thing tomorrow! :) Neal -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 8:38 PM To: Tomcat Users List Subject: RE: Tomcat - 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 redirect (http 302) to a different URL, I want it to stay at http://www.xyz.com and simply show the contents of the default page To make sure I wasn't giving you a bum steer, I did a quick test. Without any RewriteRule, if I went to a test http://host/, I would get: GET / HTTP/1.1 302 647 - GET /index.html HTTP/1.1 200 2841 - Adding: RewriteRule ^/$ /index.html [L] changed it so that I got: GET / HTTP/1.1 200 2841 - No more 302 redirect. :-) --- Noel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: SEO and servlets
Those are both very good points I hadn't considered - thank you! :) Neal -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Friday, December 06, 2002 6:35 PM To: Tomcat Users List Subject: RE: SEO and servlets On Fri, 6 Dec 2002, Cox, Charlie wrote: Date: Fri, 6 Dec 2002 08:13:20 -0500 From: Cox, Charlie [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: SEO and servlets I do a silimar thing where all my content is in a database as XML, so that the users can update their content when *they* need to(not when I get around to it). Then the html is created using xsl when requested. The way that I set this up is that I map a directory to each servlet (or sometimes multiple directories to a servlet for different functionality for another set of pages) and then use real page names. These appear to be static html pages. This allows the pagename to be a prarm for the servlet. A popular technique for supporting this sort of thing is to use path mapping with the wild card pattern. Consider a servlet that is mapped to /display/*, and a URL like this: http://www.mycompany.com/myapp/display/foo.html The /foo.html part of that URL shows up in your servlet as the extra path info, and can be used to go look up the database information and perform the translation. Your application understands that you're executing a servlet that is creating (potentially) dynamic content. Yet, to users and search engines, this appears to be a URL of a static HTML page in the display subdirectory. Is it live or is it Memorex? was a marketing slogan for a brand of audiotapes a few years ago. Only your app server knows for sure ... :-) I also do not have many forms(nor do I use struts,etc) so that is not a problem for me. This kind of dynamic content (where it changes occasionally but not often) is reasonable to index with a search engine. One thing you'll want to make sure you do is include a Date header (containing some representation of when the underlying database was last updated) in the response -- that way, browsers can also cache the rendered page and only update when the underlying data changes. You'll also want to implement the getLastModified() method in your servlet for this to work. Charlie Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: SEO and servlets
Craig, Thanks for the reponse. I know what you're saying that you wouldn't want to submit most web app pages, presuming that most of it is form data ... but in this case I have a bit of content that was placed into dynamic pages because (a) There is a common naivgation framework that is essentially included, (b) in the case of the main page there is some 'weekly specials' data that gets inserted into the content. The framework I developed presumes XsLT for the template rather than jsp, which means that I must use a servlet (in this case with my own extension), and thus the concern. So that's why I was wondering. I knew about the other issues such s have params beyond the question mark (they won't be picked up)... again another reason to use a servlet wherein *.abc would invoke the abc serlet and * could introspectively obtained as a param .. I thought that might be a way around it ... but I'm beginning to think perhaps not. :( Anyway, thanks for your thoughts. -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 6:55 PM To: Tomcat Users List Subject: Re: SEO and servlets On Wed, 4 Dec 2002, neal wrote: Date: Wed, 4 Dec 2002 22:06:53 -0800 From: neal [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: SEO and servlets I was reading on Google the other day that it supports many of the common file types including JSP ... but this led me to wonder if they index servlets without file extensions, or how about common frameworks such as Struts with the DO extensions. Does anyone know how these file types index with Google and other major engines? Different search engines follow different policies -- you'd have to ask them how their spiders are programmed. Most of them, probably, omit at least some of the following types of URLs: * URLs protected by an authentication constraint * URLs matching patterns listed in the deny list of your robots.txt file * URLs that have query parameters in them * URLs that have no-cache headers in the returned content Personally, I think it's somewhere between misleading and silly to index pages from a web *applications* (as opposed to web sites) based on an MVC framework (like Struts). Why? Because the URL that a search engine spider would submit doesn't necessarily have *anything* to do with the output that gets rendered. Consider a very common case where you have a form submit that goes to a URL ending in .../saveCustomer.do in a Struts app. If you've made any errors that get caught by the validation rules, the original input form is redisplayed. On the other hand, if you did everything correctly, the next page in your app's user interaction is displayed (probably a menu or something). But the URL is the same! Which kind of output should a search engine index? Web applications != Web sites Thanks. Neal Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
SEO and servlets
I was reading on Google the other day that it supports many of the common file types including JSP ... but this led me to wonder if they index servlets without file extensions, or how about common frameworks such as Struts with the DO extensions. Does anyone know how these file types index with Google and other major engines? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Response.ContentType - not always setting contentType in Header
Yes you are correct I believe - you must set the contentType prior to writing to out. But ... I am. And, still 2 of my more important pages are not showing the contentType as being defined...those same two pages show a contentLength of 0, and yet those same two pages seem to work perfectly fine. Well, the real reason I am worried about this is that I heard a rumor that this could affect search engine crawling - that is may prevent some engines from crawling the content. Does anyone know if this is true? Thanks. Neal -Original Message- From: David Tildesley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 12:20 AM To: Tomcat Users List Subject: RE: Response.ContentType - not always setting contentType in Header I think you cannot set contenttype after putting out any response body - so double check that you set the content type as the very first thing before sending any response body. HTH -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 27 November 2002 8:18 a.m. To: Tomcat Users List Subject: Response.ContentType - not always setting contentType in Header Does anyone know of a reason why response.setContentType() would only sometimes set my content type? I have a single control servlet which sets content type explicitly response.setContentType(text/html); just before it opens an outputStream and writes an XSLT transformation to out. For 70% of my pages the contentType is correct. For 30% of them (even the pages otherwise work perfectly fine) the header info is messed up. There is no contentType specified and contentLenght is 0. Very strange. In these pages (their control classes I do not do anything specific to the response object that is any different from the other pages. In the XsLTs I specify output as HTML on all the pages. Very confusing. Any thoughts as to why this might happen or how to correct it? I think it may be causing me search engine indexing problems. Thanks. Neal attachment: winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Response.ContentType - not always setting contentType in Header
Does anyone know of a reason why response.setContentType() would only sometimes set my content type? I have a single control servlet which sets content type explicitly response.setContentType(text/html); just before it opens an outputStream and writes an XSLT transformation to out. For 70% of my pages the contentType is correct. For 30% of them (even the pages otherwise work perfectly fine) the header info is messed up. There is no contentType specified and contentLenght is 0. Very strange. In these pages (their control classes I do not do anything specific to the response object that is any different from the other pages. In the XsLTs I specify output as HTML on all the pages. Very confusing. Any thoughts as to why this might happen or how to correct it? I think it may be causing me search engine indexing problems. Thanks. Neal attachment: winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Response.ContentType - not always setting contentType in Header
Definitive classes. And I have (and still am) going through the XSLT and the page classses (the classes that the control servlet calls specific to the requested page) with a fine tooth comb. The only thing that the 3 problem pages seem to have in common that I have not yet eliminated is that they (a) read from the request header info, and (b) do a couple of redirects if needed based upon that request header info. But those conditions should not be applicable to a simple request and thus should not affect the output. In fact, the status code is 200 (not 302 in the case of a redirect). So then, I guess the only really difference that I'm seeing so far is that they read from the request header. but I can't imagine that this would make a difference. :( Thanks. Neal -Original Message- From: micael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 11:27 AM To: Tomcat Users List Subject: Re: Response.ContentType - not always setting contentType in Header Is it seemingly random or is it definitive classes Neal? At 11:17 AM 11/26/2002 -0800, you wrote: Does anyone know of a reason why response.setContentType() would only sometimes set my content type? I have a single control servlet which sets content type explicitly response.setContentType(text/html); just before it opens an outputStream and writes an XSLT transformation to out. For 70% of my pages the contentType is correct. For 30% of them (even the pages otherwise work perfectly fine) the header info is messed up. There is no contentType specified and contentLenght is 0. Very strange. In these pages (their control classes I do not do anything specific to the response object that is any different from the other pages. In the XsLTs I specify output as HTML on all the pages. Very confusing. Any thoughts as to why this might happen or how to correct it? I think it may be causing me search engine indexing problems. Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Response.ContentType - not always setting contentType in Header
Micael,
yeah, here's the code I've written that I believe to be applicable. The
controlServlet (the first snippet) sets the contentType, gets the out and
writes to the writer, the output of the XSLT transformation. This is done
by calling transformTOWriter (which is in a dff't class). Note, that I have
provided the overridden version of this method as well so you can see how
the one applicable to the first snippet basically just aliases to the 3 arg
version of the mehtod.
This seems to work with most classes just not all. :(
In regard to a couple of questions as to whether the contentLength was set
to 0 upon refreshing - na ... its this way the first time its called and
even if I do an explicit refresh. The content comes out fine, displays
fine, but the lenght is still 0 and the contentType is not there. FYI,
here's the tool I'm using to view this info:
http://www.searchengineworld.com/cgi-bin/sim_spider.cgi
CODE REFERRED TO ABOVE
//Preperare publish
response.setContentType(text/html);
PrintWriter out = response.getWriter();
XslTool xt = new XslTool();
xt.transformToWriter(xml, xsl, out, xslParams);
public void transformToWriter(Document xml, Transformer xsl, Writer out,
Hashtable parameters)
throws TransformerException {
if (parameters != null) {
for (Enumeration e = parameters.keys() ; e.hasMoreElements() ;) {
String key = (String)e.nextElement();
xsl.setParameter(key, (String)parameters.get(key));
}
}
transformToWriter(xml,xsl,out);
}
/** Transform specified DOM against specified transformed and out to a
writer. */
public void transformToWriter(Document xml, Transformer xsl, Writer out)
throws TransformerException {
xsl.transform(new DOMSource(xml), new StreamResult(out));
}
-Original Message-
From: micael [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 11:48 AM
To: Tomcat Users List
Subject: RE: Response.ContentType - not always setting contentType in
Header
Can you provide the relevant code from one that does not work and one that
does work? Or, would you have to kill me if you did that?
At 11:35 AM 11/26/2002 -0800, you wrote:
Definitive classes. And I have (and still am) going through the XSLT and
the page classses (the classes that the control servlet calls specific to
the requested page) with a fine tooth comb. The only thing that the 3
problem pages seem to have in common that I have not yet eliminated is that
they (a) read from the request header info, and (b) do a couple of
redirects
if needed based upon that request header info. But those conditions should
not be applicable to a simple request and thus should not affect the
output.
In fact, the status code is 200 (not 302 in the case of a redirect). So
then, I guess the only really difference that I'm seeing so far is that
they
read from the request header. but I can't imagine that this would make a
difference. :(
Thanks.
Neal
-Original Message-
From: micael [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 11:27 AM
To: Tomcat Users List
Subject: Re: Response.ContentType - not always setting contentType in
Header
Is it seemingly random or is it definitive classes Neal?
At 11:17 AM 11/26/2002 -0800, you wrote:
Does anyone know of a reason why response.setContentType() would only
sometimes set my content type?
I have a single control servlet which sets content type explicitly
response.setContentType(text/html);
just before it opens an outputStream and writes an XSLT transformation to
out. For 70% of my pages the contentType is correct. For 30% of them
(even
the pages otherwise work perfectly fine) the header info is messed up.
There
is no contentType specified and contentLenght is 0. Very strange. In
these
pages (their control classes I do not do anything specific to the
response
object that is any different from the other pages. In the XsLTs I
specify
output as HTML on all the pages. Very confusing.
Any thoughts as to why this might happen or how to correct it? I think
it
may be causing me search engine indexing problems.
Thanks.
Neal
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
Micael
---
This electronic mail transmission and any accompanying documents contain
information belonging to the sender which may be confidential and legally
privileged. This information is intended only for the use of the
individual or entity to whom this electronic mail transmission was sent as
indicated above. If you are not the intended recipient, any disclosure,
copying, distribution, or action taken in reliance on the contents of the
information contained in this transmission is strictly prohibited. If you
have received this transmission in error, please delete the message. Thank
you
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED
tomcat redirects to default page
Tomcat autmatically redirects from the root url to the defualt page of the URL: www.myurl.com - www.myurl.com/index.jsp Does anyone know how to prevent it from doing this? I would rather that it show the default page but not redirect the url to www.myurl.com/index.jsp. Is this possible? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: tomcat redirects to default page
Yeah, I mean the default page is what you specify it to be right? Ok, here's what I mean: I was using BCentral.com and they have a tool for scoring your website ranking on the major search engines. I typed in my URL (www.myurl.com) and bCentral came back with a message to the effect of Your default page is a redirect page which redirects to www.myurl.com/index.jsp. Redirects confuse search engines and can hurt your rankings. I don't know a great deal about search engines but this was a concern upon reading it. That said, I looked through the goole listings for a common topic and saw that most sites listed the root url without the default page name. With a lot of web servers such as MS IIS, this is not a problem and so I presume it to not be a problem with a lot of other servers as well. So I then presume there must be a way to get Tomcat to behave in line with this preferred expectation. Any thoughts? Thanks! Neal -Original Message- From: Carsten Ziegert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 2:40 AM To: Tomcat Users List Subject: Re: tomcat redirects to default page Neal, I suppose index.jsp *is* the default page. Welcome pages are defined in conf/web.xml: welcome-file-list welcome-fileindex.html/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.jsp/welcome-file /welcome-file-list But I dont' know if there is a priority specification. You could either rename the file index.jsp or delete the line from web.xml, but you'll keep in mind that web.xml is valid for *all* web applications. Carsten Am Montag, 18.11.02, um 11:17 Uhr (Europe/Berlin) schrieb neal: Tomcat autmatically redirects from the root url to the defualt page of the URL: www.myurl.com - www.myurl.com/index.jsp Does anyone know how to prevent it from doing this? I would rather that it show the default page but not redirect the url to www.myurl.com/index.jsp. Is this possible? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Carsten Ziegert Hannover Medical School, Dept. of Hematology and Oncology Carl-Neuberg-Straße 1, 30625 Hannover University of Applied Sciences, Faculty of Information Sciences Ricklinger Stadtweg 120,30459 Hannover http://summit-bmt.fh-hannover.de -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat + Search Engines
I have been looking into search engine submission. It sounds as though most engines to not like urls that simply redirect to another url. That said, I am getting the impression that Tomcat's default redirection to the default page when you type in the base url (e.g. www.myurl.com - www.myurl.com/index.jsp) is going to knock me down a few pegs on some of the search engines. a. Is this true? b. Is there a way around it or do I have to submit my url at www.myurl.com/index.jsp, rather than www.myurl.com? Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
auto-redirect to default page - undesired
Tomcat appears to auto-redirect to the default page rather than leaving the url of the default url (www.mysite.com) while displaying the default page. In otherwords, if the url (www.mysite.com) is requested, the url is actually redirected (the url of the window will change) to www.mysite.com/index.jsp. This presumes use of tomcat as standalone. From what I have been reading this can have adverse effects on search engine placement and is thus not a desired effect. Does anyone know how to configure tomcat to behave as most other web servers and *not* redirect the user? I think the difference here may be to forward the user versus redirecting them. Thanks. Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
