Re: Apache Accessing Tomcat Issue

2013-03-31 Thread Rainer Jung
On 30.03.2013 21:53, Chris Arnold wrote: > See above and ended up having to comment this out as it is not supported in > the version of mod_jk i am using. > Apache finally started after commenting those out and changing the port. And > i can now access http://share.domain.com > Ranier, thank you

Re: Apache Accessing Tomcat Issue

2013-03-30 Thread Chris Arnold
On 30.03.2013 12:43, Chris Arnold wrote >>The following param doesn't exist in your old version: > # error_escalation_time: seconds, default = recover_time/2 (=30) > # Determines, how fast a detected error should switch from > # local error state to global error state > # Since: 1.2.28 > worker.b

Re: Apache Accessing Tomcat Issue

2013-03-30 Thread Rainer Jung
On 30.03.2013 12:43, Chris Arnold wrote: > Here is the modified virtualhost file: > > ServerName share.domain.com > > #RewriteEngine On > #RewriteCond %{REQUEST_URI} !^/share/ > #RewriteCond %{HTTPS} on > #RewriteRule ^/. http://share.domain.com/share/ [P] > JkMount

Re: Apache Accessing Tomcat Issue

2013-03-30 Thread Chris Arnold
On 29.03.2013 18:02, Chris Arnold wrote: >http://share.domain.com and get the required results (which is >http://share.domain.com/share) >>Let's stick to mod_jk for the moment. I think you are close. OK Here is the modified virtualhost file: ServerName share.domain.com #RewriteEng

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Rainer Jung
On 29.03.2013 18:02, Chris Arnold wrote: > This thread is getting kinda messy so i am going to snip a bunch of stuff and > answer your latest info. Good. >> So mod_proxy is loaded but you don't want to use it to access alfresco, >> instead just mod_jk, right? Then don't use any ReWriteRule with

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Chris Arnold
This thread is getting kinda messy so i am going to snip a bunch of stuff and answer your latest info. >So mod_proxy is loaded but you don't want to use it to access alfresco, >instead just mod_jk, right? Then don't use any ReWriteRule with the [P} >flag or any Proxy... directive. No, if this c

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Rainer Jung
On 29.03.2013 13:10, Chris Arnold wrote: > On 29.03.2013 00:24, Chris Arnold wrote: >> >> # The following line mounts all JSP files and the /servlet/ uri to tomcat >> #JkMount /servlets-examples/servlet/* ajp13 >> JkMount /share/*.jsp ajp13 > >>> Note that you only forward JSP-Requests

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Chris Arnold
>>What's the request you send? i assume you are asking for the link? Which is http://share.domain.com >>What's the expected response a login page >>and what's the actual response? Now, it is a 403: [Fri Mar 29 08:15:24 2013] [error] [client pub ip] Directory index forbidden by Options directive:

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Chris Arnold
On 29.03.2013 00:24, Chris Arnold wrote: > > # The following line mounts all JSP files and the /servlet/ uri to tomcat > #JkMount /servlets-examples/servlet/* ajp13 > JkMount /share/*.jsp ajp13 >>Note that you only forward JSP-Requests here. might be OK, depending on >>the application

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Rainer Jung
On 29.03.2013 00:24, Chris Arnold wrote: > Apache Tomcat/7.0.30 on SLES11 SP2. I am trying to configure access to a > webapp using http://share.domain.com. This webapp uses port 8080 and works > fine from inside the LAN. However, we have an apache2 server acting as a > proxy and we want users to

Re: Apache Accessing Tomcat Issue

2013-03-29 Thread Igor Cicimov
On 29/03/2013 10:29 AM, "Chris Arnold" wrote: > > Apache Tomcat/7.0.30 on SLES11 SP2. I am trying to configure access to a webapp using http://share.domain.com. This webapp uses port 8080 and works fine from inside the LAN. However, we have an apache2 server acting as a proxy and we want users to

Apache Accessing Tomcat Issue

2013-03-28 Thread Chris Arnold
Apache Tomcat/7.0.30 on SLES11 SP2. I am trying to configure access to a webapp using http://share.domain.com. This webapp uses port 8080 and works fine from inside the LAN. However, we have an apache2 server acting as a proxy and we want users to not have to type in a port number. Now when acc