Re: Can you use Tomcat when you are not on line?
It is more than likely you browser needs to be told localhost is local. Go to a command line and ping localhost and see if it works - Original Message - From: Rhino [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 06, 2005 6:42 PM Subject: Re: Can you use Tomcat when you are not on line? You are correct. I use Tomcat on XP via localhost:8080 all the time and it works fine. I am using a DSL connection that is on all the time so I suppose it is possible that Tomcat is using that somehow but I'd be surprised Perhaps you should post the exact error message you are getting and some of your configuration information so that people can figure out what is *really* causing your problem. Rhino - Original Message - From: Walter Lee [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Wednesday, April 06, 2005 11:44 AM Subject: Can you use Tomcat when you are not on line? I have Tomcat installed on W2K and it says it is installed correctly. When I try the examples it tells me that I must be on line. If I am using localhost:8080 why does it need to be on line? -- -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 05/04/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 05/04/2005 - 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: Troubleshooting Virtual Hosts with Tomcat 5 standalone mode...
This is in my server.xml the directory is webapps/by-m. It works also on a linux box. It is inside the engine. Host name=by-m debug=0 appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false Context path= docBase=by-m debug=5 reloadable=true /Context /Host - Original Message - From: Jeff Duska [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Monday, April 04, 2005 7:45 PM Subject: Troubleshooting Virtual Hosts with Tomcat 5 standalone mode... I'm trying to setup a couple of virtual hosts using Tomcat in stand alone mode. I'm having a hell of a time to get this working correctly. I've tried several configs, but they all fail. I started with the goal of having a user directory for each virtual host. For example, for the sample domain1.com the appbase would be /home/domain/webapps. I setup my server.xml file to have the following host settings Host name=domain1.com debug=0 appBase=/home/domain/webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false Context path= docBase=./ /host This is pretty much cut and past from Tomcat: The Definitive Guide from Safari Online. This did not work. I would get just get a blank webpage. I then tried to update the host file. I didn't see why I'd need to do that since my DNS setup at Mydomain.com was working for ssh. I add domain1.com to the line for my localhost. I restarted Tomcat. No change. I am able to run the system on port 80 using just the localhost default settings. I figured I just did something wrong. I switched to this directions http://www.ex-parrot.com/~pete/tomcat-vhost.html This didn't worked either. When I looked at the requests in in Safari, it showed this as a bad request. I can telnet domain1.com 80. When I try GET index.jsp or index,html or /. Nothing happens. No error. It just closed the connection as if everything was working fine. I tried lynx from the server prompt. It gives a http 400 error, I think. It flashes by so fast I'm not sure. The catalina.out has no errors. I have my DNS setup via mydomain.com dns management tool. I have my A record pointing to the address. I don't think I need to do anything else. I'm at a loss of what to do now to troubleshoot this problem. I searched the mail list and the website nothing has jumped out at me. So, I hoping some kind soul might give me some pointers. What kills me is I'm sure this is something obvious I missed or not seeing. Thanks, Jeff Duska [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: SSL configuration question
Answer to number 2 is edit your server.xml change 8443 to 443 in the ssl section also check that the the normal port redirects to 443. Where you see 8443 change to 443. 2 changes in your server.xml. - Original Message - From: Faine, Mark [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Thursday, March 31, 2005 7:44 PM Subject: SSL configuration question Solaris 8, Tomcat 5.0.28 I've configured my tomcat installation with my SSL key from Entrust and it is working (sort of). 1. It is not correctly configured. It shows my organization as both issued to and issue by when I view the certificate information. Could someone explain what I have done wrong and how to correct it. 2. It must be run on port 8443 because I need to run it as a user other than root. How can I bypass this limitation and run it on the standard 443 port? Thanks, -Mark - 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: SSL configuration question
I thought the two are not related my key is stored in the java keystore. I did everything with keytool, part of java. Tomcat only needs the password and name. The SSL certificate is not generated for or by tomcat. Hein - Original Message - From: Mikhail Kruk [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Thursday, March 31, 2005 11:42 PM Subject: RE: SSL configuration question The certificate I imported was not self-signed (or should not be). It is what I received back from Entrust after submitting a CSR. It was already in use on Apache before I decided not to use Apache anymore. It worked before on Apache. I shut down apache and was intending to use the cert on only Tomcat. You can't easily import the certificate that was generated for Apache into Tomcat -- you need to have the prvite key part in your keystore and your private key is in your Apache. There must be a way to get the key from Apache and move it to Tomcat, but I'm not sure what it is. This might help: http://kb.thawte.com/thawte/thawte/esupport.asp?id=vs24694 Thanks, -Mark -Original Message- From: Sasisekar S Sundaram [mailto:[EMAIL PROTECTED] Sent: Thursday, March 31, 2005 2:43 PM To: Tomcat Users List Subject: Re: SSL configuration question It shows both issued to and issue by because it is a self signed certificate. when you get you certificate authorized by some one like verisign, and then import that certificate into your keystore, you'll get issued by as that certifying authority's name. - Original Message - From: Faine, Mark [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Thursday, March 31, 2005 1:13 PM Subject: RE: SSL configuration question Thanks, I tried that before and got a permission error, but it works now. -Mark -Original Message- From: Hein Behrens [mailto:[EMAIL PROTECTED] Sent: Thursday, March 31, 2005 12:41 PM To: Tomcat Users List Subject: Re: SSL configuration question Answer to number 2 is edit your server.xml change 8443 to 443 in the ssl section also check that the the normal port redirects to 443. Where you see 8443 change to 443. 2 changes in your server.xml. - Original Message - From: Faine, Mark [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Thursday, March 31, 2005 7:44 PM Subject: SSL configuration question Solaris 8, Tomcat 5.0.28 I've configured my tomcat installation with my SSL key from Entrust and it is working (sort of). 1. It is not correctly configured. It shows my organization as both issued to and issue by when I view the certificate information. Could someone explain what I have done wrong and how to correct it. 2. It must be run on port 8443 because I need to run it as a user other than root. How can I bypass this limitation and run it on the standard 443 port? Thanks, -Mark - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ugly urls
http://tuckey.org/urlrewrite/ Does the same for Tomcat. No need for Apache - Original Message - From: Jason Bainbridge [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, March 23, 2005 6:45 PM Subject: Re: ugly urls On Wed, 23 Mar 2005 16:47:19 +, Didier McGillis [EMAIL PROTECTED] wrote: Hi everyone I wanted to see if in JSP or Tomcat there was an easy way to transform ugly urls into pretty urls. So taking category.jsp?catid=12type=2 and changing it to category/catid/12/type/2? Best way would be to put Apache (Webserver) in front of tomcat and then use mod_rewrite rules. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.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]
Re: ugly urls
- Original Message - From: Mark Leone [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Thursday, March 24, 2005 2:46 AM Subject: Re: ugly urls Don't know if this will help you or not, but Web Services Description Language (WSDL) provides a standard way to create URLs that encode parameters passed to web apps. If you need to publish your web app URLs or make them available to lots of people, or if clients want to programmatically ingest your published URLs, WSDL can be a convenient mechanism. Most people think of the SOAP bindings that describe web services when they think of WSDL, but it also provides HTTP bindings for exposing web apps. Go to http://www.w3.org/TR/wsdl#_http and see Section 4. Excerpt below. 4. HTTP GET POST Binding WSDL includes a binding for HTTP 1.1's GET and POST verbs in order to describe the interaction between a Web Browser and a web site. This allows applications other than Web Browsers to interact with the site. The following protocol specific information may be specified: * An indication that a binding uses HTTP GET or POST * An address for the port * A relative address for each operation (relative to the base address defined by the port) 4.1 HTTP GET/POST Examples The following example shows three ports that are bound differently for a given port type. If the values being passed are part1=1, part2=2, part3=3, the request format would be as follows for each port: port1: GET, URL=http://example.com/o1/A1B2/3; port2: GET, URL=http://example.com/o1?p1=1p2=2p3=3 port3: POST, URL=http://example.com/o1;, PAYLOAD=p1=1p2=2p3=3 Hein Behrens wrote: http://tuckey.org/urlrewrite/ Does the same for Tomcat. No need for Apache - Original Message - From: Jason Bainbridge [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, March 23, 2005 6:45 PM Subject: Re: ugly urls On Wed, 23 Mar 2005 16:47:19 +, Didier McGillis [EMAIL PROTECTED] wrote: Hi everyone I wanted to see if in JSP or Tomcat there was an easy way to transform ugly urls into pretty urls. So taking category.jsp?catid=12type=2 and changing it to category/catid/12/type/2? Best way would be to put Apache (Webserver) in front of tomcat and then use mod_rewrite rules. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.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] - 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]
