Scalix 11 - Permissions error with tomcat/apache

[scalar1234]

Hi Florian,

the error 403 comes from apache, since it is located in
/var/log/apache2/error.log

At the moment I opened port 8080 for tomcat
and furthermore I reverted to apache 2.0.
I will try to install and configure the JK-module by hand.

Kind regards
Andreas

[hkurent]

Hi,

consulting a friend of mine, he proposed the following fix
in /etc/apache2/mods-enabled/proxy.conf

<IfModule mod_proxy.c>
#turning ProxyRequests on and allowing proxying from all may allow
#spammers to use your proxy to send email.

ProxyRequests Off

<Proxy *>
AddDefaultCharset off
Order deny,allow
Deny from all
### change here to allow local network ###
Allow from .your-domain-or-network-here.de
</Proxy>

# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block

ProxyVia On
</IfModule>

The change below ### should enable the proxy.
Well, it does it here.

Please let me know if it worked for you!

Regards,
Hans

[scalar1234]

Hello Hans,

YES, it worked.
The complete installation of Scalix 11.0.1.22 and Apache 2.2.3 went through without any error.

When I left proxy.conf unchanged I got error 403 again.

As soon as had edited proxy.conf by allowing my client
and had restarted apache IT WORKED!!!!

THANK YOU YERY YERY MUCH!!!

[mmain]

I am in the process of building a new machine running FC5 to be able to take advantage of Scalix 11 amongst other things, but had to 'downgrade' from Apache 2.2.x to Apache 2.0.59 to be able to continue using frontpage extensions. I now see that I am going to have difficulty with mod_proxy_ajp not being possible and I have subsequently compiled in mod_jk support. If I open the Debian tarball, will I be able to get the Scalix configuration information from there?

Regards,

Martin

[florian]

You will need to build a scalix-tomcat-connector package that satisfies the dependencies the scalix-tomcat package has on it, but works on fc5 and Apache 2.0. Very likely, the package for RHEL4 can be a good starting point or might even work (not sure about the compatibility of the exact Apache version though)

If you have that as an RPM, the rest of the Fedora Core 5 install should just run fine, just go for a customized install and don't reinstall/upgrade the connector package.

Of course, this will be somewhat messy and unsupported. And all that to get the worst web design package on the planet running?

Florian.