On Tue, Feb 8, 2011 at 18:57, Glenn Little <[email protected]> wrote: > Why do you need to go through the chain of ports (8009 -> 8443)? > First, is the 8443 necessary if. in apache's conf, you redirect all > port 80 requests over to ssl 443? Second, what is "ajp" for? > > This may be simple-minded, but if a browser can talk directly to > tomcat on 8080, why can't apace do so as well?
Don't worry, it's a valid question. Technically, you can just talk to Tomcat directly on 8080 or 8443. Or you can run even tomcat on ports 80 and 443. I justify using Apache with 2 reasons: 1) I don't want to run Tomcat as root, so I run Apache as root on ports 80 and 443 instead. 2) I can use mod_rewrite in Apache Regarding HTTPS in Tomcat: Yes, you can just do SSL in Apache. I currently cannot think of any disadvantages of that approach, except that if you remove Apache, you cannot talk directly to Tomcat in HTTPS. Regarding AJP: I'm also familiar with Tomcat just because of DSpace, so I'll refer you to the docs. AJP is used to communicate with Apache instead of HTTP probably for performance reasons (AJP is binary, HTTP is text) and it somehow supports load balancing. http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html > Also, it looks like the "Contexts" you're setting up in tomcat are a > little like rewrite rules or aliases in apache. Is there a reason you > do them as contexts instead? DSpace components such as XMLUI, JSPUI, OAI, SOLR and others are designed as stand-alone applications running over the DSpace API. You can choose to run or not to run any of them. In Tomcat (or rather in the Servlet specification, I assume), applications run in contexts. More info on contexts: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html > Do the contexts take care outgoing urls too, or is it more like the > way it looks to me, that's what the dspace configs (dspace.url etc) > are really there for? Only as much as defining the "base url" of the application. For rewriting, I would use mod_rewrite in Apache. Regards, ~~helix84 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
