I'm surprised that the Alfresco team is still giving-out advice that
was appropriate in the mid-2000s.
Some notes:
1. Don't put Context in server.xml. Just don't.
2. debug hasn't been used in ... forever.
3. path= is bad, and isn't necessary if you follow #1
It did not work so i took it out
The best possible setup here is to set up httpd with more than one
VirtualHost (and SNI, since you are using HTTPS) with the correct
hostnames, etc., and only use JkMount from the share2 VirtualHost.
Then, re-name your application from share.war to ROOT.war and
re-deploy it into Tomcat. Use
If the application can't handle that (try it!), you'll have to make
other arrangements.
According to:
https://wiki.alfresco.com/wiki/Deploying_To_Server
that is not even necessary. I understand that link is a years old and talks
about tomcat 6 but the general idea is the same. I will try to
Yeah, that document is evidently a pack of lies. Specifically,
the path and docbase attributes in Context are ignored in
META-INF/context.xml files, and you really shouldn't have your
Context anywhere else (except in
conf/[engine]/[host]/[appname].xml, which behaves almost the same
way).
Yeah, that document is evidently a pack of lies. Specifically, the
path and docbase attributes in Context are ignored in
META-INF/context.xml files, and you really shouldn't have your
Context anywhere else (except in conf/[engine]/[host]/[appname].xml,
which behaves almost the same way).
If you won't re-name the web application, I think redirects will be
your best bet. If a client requests http(s)://share2.domain.tld/, you
should redirect them to https://share2.domain.tld/share/ and then
JkMount /share/* worker1. You can redirect using RedirectPermanant
or a few other things
*sigh*
If you only want to proxy for one VirtualHost, then only set up
JkMounts in that one VirtualHost.
Like this:
VirtualHost *:80
ServerName share2..xxx
JkMount /* worker1 (or balancer, whichever you want)
/VirtualHost
Maybe I wasn't clear in my other reply, the
What you want is:
JkMount /share2/* worker1
or maybe:
JkMount /share2/* balancer
workers.properties defines the workers (target host/port, connection
options, etc.) and the JkMount directives in httpd.conf map URL
patterns to those workers.
So JkMount /* proxied everything and we only need
What you want is:
JkMount /share2/* worker1
or maybe:
JkMount /share2/* balancer
workers.properties defines the workers (target host/port, connection
options, etc.) and the JkMount directives in httpd.conf map URL
patterns to those workers.
So JkMount /* proxied everything and we only need
+1
And also, could you specify again what URL you are requesting in the browser,
which you
would expect to be proxied to Tomcat ?
https://share2.domain.tld
Looking at the log you just showed, it seemed that the only requests ever
passed through
mod_jk for evaluation, where things like
Chris,
On 1/21/15 5:56 PM, Chris wrote:
You must have changed something since your original configuration. Do
you have JkMount ajp13 somewhere? You need to use the worker name
and not the protocol name.
Can you post your updated workers.properties file, and related
httpd.conf configurations?
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c
which includes tomact 7.x i believe. SLES 11 has apache 2.2.10. SLES 12 has
apache 2.4 and we use the same version of alfresco
No JkMount?
mod_jk uses the JkMount directive to decide, which requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is used in your
Apache web server config to serve the requests for /myapp.
When i look at the existing
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/share/
RewriteRule ^/(.*) https://share.domain.tld:8443/share/ [P]
That will forward any
Am 31.10.2013 20:30, schrieb Chris Arnold:
mod_rewrite is what's adding the extra /share/
RewriteRule ^/(.*) https://192.168.123.3:8443/share/$1 [P]
should be something like either:
RewriteRule ^/(.*) https://192.168.123.3:8443/$1 [P]
This takes me to the tomcat home page, /
If you want
So i was not able to get any of those to work. So i moved to the third option,
mod_jk. It is loaded. I make the changes in my vhost:
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond
Starting over since i can not seem to get this to work with tomcat or apache.
So what i have now that IS somewhat working is:
#This rewrites https://share.anydomain.tld to our mail server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteRule
mod_rewrite is what's adding the extra /share/
RewriteRule ^/(.*) https://192.168.123.3:8443/share/$1 [P]
should be something like either:
RewriteRule ^/(.*) https://192.168.123.3:8443/$1 [P]
This takes me to the tomcat home page, /
or:
RewriteRule ^/share/(.*)
Chris,
Thank you for taking the time to help me in securing tomcat. I called godaddy
and they instructed me to download the tomcat cert, which i did, and follow
their provided instructions:
Let us first determine which connector do you have configured (BIO, NIO
or APR), because HTTPS configuration depends on connector type. Could
you send your server.xml with comments and sensitive information removed?
?xml version='1.0' encoding='utf-8'?
!--
Licensed to the Apache Software
Tomcat 7.0.42 on SLES11. I am following
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration to secure
tomcat. I have uncommented the SSL HTTP section. The configuration section of
that doc, importing the certificate: i have a go daddy bundle in crt format. I
can download the
Chris,
On 26.10.2013 23:39, Chris Arnold wrote:
Tomcat 7.0.42 on SLES11. I am following
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration to
secure tomcat. I have uncommented the SSL HTTP section. The configuration
section of that doc, importing the certificate: i have
Hi Matt,
Hi Chris,
You probably want to be using ServerAlias here, iirc..
Changed back to ServerAlias
#This rewrites https://share.anydomain.tld to our alfresco server
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
Okay, I'll take a bite at the obvious.
Chris,
mod_proxy_ajp and mod_jk are roughly equivalent though with wildly
differing configuration syntax. Also, mod_jk has quite a few
additional options that have made it always the right choice for me.
Using mod_rewrite seems completely unnecessary.
Something that you are doing that
If you are sure that httpd Virtual Hosting is working properly (e.g.you can
request the proper, say, index.html given a sub-domain), then getting Tomcat to
work should not be terribly hard.
Can you confirm that VH is working in httpd?
Yes, VH's are working fine. We have a number of
I didn't know you were running a 3rd-party application. Do you need
the application to behave differently given a particular client? If
not, there's nothing to do. If so, you probably need to ask the
Alfresco folks how to do that. I personally know nothing about
Alfresco, though there may be some
Chris,
If you just need 1 deployed webapp, then simply change your webapp to
sniff the client's name from the URL. You don't need to change
anything: you still only need one (default) virtual host in Tomcat,
and you can do whatever you want (e.g. single virtual host) in httpd.
Maybe i need to
Chuck,
On 9/13/13 4:38 PM, Caldarale, Charles R wrote:
From: Chris Arnold [mailto:carn...@electrichendrix.com] Subject:
Multi-URL Access 1 Webapp
Tomcat 7.0.3 i believe
Not bloody likely - 7.0.3 was never released. If you really are
running on 7.0.3, you need to upgrade ASAP.
We have
Tomcat 7.0.3 i believe on SLES11 SP2. We have a web app that you access from
http://domain.tld/share. What we want to do is have clients access the same web
app only from http://share.domain.tld. The domain part of that URL will change
per client. So, some will get to it like
I am not sure if this is a Tomcat issue or an apache issue, so i will ask on
both lists.
We have tomcat 6.03 on SLES11 and have content/webapp that we want to server to
multiple domains. We have 1 domain working using http://share.domain1.com. What
we want is access to this same webapp using
- Original Message -
From: Chris Arnold carn...@electrichendrix.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Thursday, April 4, 2013 12:28:02 PM
Subject: Serve same content to multiple URL's
I am not sure if this is a Tomcat issue or an apache issue, so i will ask on
both
On Apr 4, 2013, at 2:38 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 4/4/13 12:28 PM, Chris Arnold wrote:
I have tried to add a second worker (worker2) in workers.properties
and added a virtualhost like: Here
On Apr 4, 2013, at 4:45 PM, Igor Cicimov icici...@gmail.com wrote:
You just need to create Alias in the existing VirtualHost in Apache and the
Host in Tomcat.
So in the existing apache virtualhost, I need to make an alias entry? Like so:
VirtualHost *:80
ServerName share.domain.com
I didn't think I needed a second worker but because the working
config only worked for http://share.domain1.com and nothing else, I
wanted to verify it should work or I needed another worker and you
verified I do not need another worker and in fact, the existing
config for
I didn't think I needed a second worker but because the working
config only worked for http://share.domain1.com and nothing else, I
wanted to verify it should work or I needed another worker and you
verified I do not need another worker and in fact, the existing
config for
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:
VirtualHost *:80
ServerName share.domain.com
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
I thought i would understand how to config a 2nd domain to access the same
content after configuring for the first domain but that proved wrong. I have
multiple domains that need to access the same content. For example,
http://share.domain1.com should result in http://share.domain1.com/share
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
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:
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 can
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
44 matches
Mail list logo
