issues

David_C_Rankin 2014-04-02 22:30:16 UTC #1

Ralf, Nathan, All,

After move to apache 2.4, egw 1.8svn continues to function with mod_php.
(testing is still underway) However, mod_php requires modifying the default
apache 2.4 config and removing mpm_event_module and reverting to
mpm_prefork_module due to mod_php not being threadsafe. As such there is a
discussion among distributions to drop mod_php.

Can eGroupWare work without mod_php? Will it work running apache 2.4 on the
default mpm_event_module with mod_fastcgi + php-fpm?

I have not yet tested and before doing so thought I would check here to see if
anyone has/is currently running apache 2.4 with this new module mix. Thanks for
any response. If nobody has tested, then I’ll test and report back. Let me know.
Thanks.

–
David C. Rankin, J.D.,P.E.

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Ralf_Becker_Stylite 2014-04-03 06:37:36 UTC #2

Hi David,

Ralf, Nathan, All,

After move to apache 2.4, egw 1.8svn continues to function with mod_php.
(testing is still underway) However, mod_php requires modifying the default
apache 2.4 config and removing mpm_event_module and reverting to
mpm_prefork_module due to mod_php not being threadsafe. As such there is a
discussion among distributions to drop mod_php.

Can eGroupWare work without mod_php? Will it work running apache 2.4 on the
default mpm_event_module with mod_fastcgi + php-fpm?

We use php-fpm (together with Lighttpd) in our own EGroupware hosting
and for big customers.

There were some problems around WebDAV and Cal/CardDAV. I think the only
one left is basic auth, which requires a rewrite rule as documented in:

http://svn.stylite.de/viewvc/egroupware/branches/1.8/phpgwapi/inc/class.egw_digest_auth.inc.php?view=markup

I have not yet tested and before doing so thought I would check here to see if
anyone has/is currently running apache 2.4 with this new module mix. Thanks for
any response. If nobody has tested, then I’ll test and report back. Let me know.
Thanks.

Last Ubuntu already used Apache 2.4.

Ralf

Ralf Becker
Director Software Development

Stylite AG

Morschheimer Strasse 15 | Tel. +49 6352 70629 0
D-67292 Kirchheimbolanden | Fax. +49 6352 70629 30

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 31158 Kaiserslautern Germany

David_C_Rankin 2014-04-04 07:53:57 UTC #3

Hi David,

Ralf, Nathan, All,

After move to apache 2.4, egw 1.8svn continues to function with mod_php.
(testing is still underway) However, mod_php requires modifying the default
apache 2.4 config and removing mpm_event_module and reverting to
mpm_prefork_module due to mod_php not being threadsafe. As such there is a
discussion among distributions to drop mod_php.

Can eGroupWare work without mod_php? Will it work running apache 2.4 on the
default mpm_event_module with mod_fastcgi + php-fpm?
We use php-fpm (together with Lighttpd) in our own EGroupware hosting
and for big customers.

There were some problems around WebDAV and Cal/CardDAV. I think the only
one left is basic auth, which requires a rewrite rule as documented in:

http://svn.stylite.de/viewvc/egroupware/branches/1.8/phpgwapi/inc/class.egw_digest_auth.inc.php?view=markup

Thank you Ralf,

I will have to check to see if this conflicts with the current per-directory
rewriting that my server does. I currently have rewrites for egw configured to
force http->https rewriting for remote IPs. For example:

eGroupWare Directory, SSL and Inclusion for eGroupWare SyncML

<Directory “/srv/http/htdocs/egroupware”>

RewriteEngine On
RewriteBase /
RewriteCond %{REMOTE_ADDR} !^192.168.7.
RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]

<Location /egroupware/rpc.php>
php_value mbstring.func_overload 0
Order allow,deny
Allow from all

Can I just add this rewrite rule after my existing rule?

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REMOTE_ADDR} !^192\.168\.7\.
    RewriteCond %{HTTPS} !=on
    RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
</IfModule>

I believe the <Location /egroupware/rpc.php> config for egw SyncML is from the
1.2 or 1.4 days. Is this still required? Thanks for all your hard work.

David C. Rankin, J.D.,P.E.

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Ralf_Becker_Stylite 2014-04-04 08:49:02 UTC #4

Hi David,

Thank you Ralf,

I will have to check to see if this conflicts with the current per-directory
rewriting that my server does. I currently have rewrites for egw configured to
force http->https rewriting for remote IPs. For example:

eGroupWare Directory, SSL and Inclusion for eGroupWare SyncML

<Directory “/srv/http/htdocs/egroupware”>

RewriteEngine On
RewriteBase /
RewriteCond %{REMOTE_ADDR} !^192.168.7.
RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]

<Location /egroupware/rpc.php>
php_value mbstring.func_overload 0
Order allow,deny
Allow from all

Can I just add this rewrite rule after my existing rule?
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REMOTE_ADDR} !^192\.168\.7\.
    RewriteCond %{HTTPS} !=on
    RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
</IfModule>

Should work

I believe the <Location /egroupware/rpc.php> config for egw SyncML is from the
1.2 or 1.4 days. Is this still required?

Only if you still use SyncML. It will no longer be included in 14.1 in
favor of eSync (ActiveSync protocol).

Thanks for all your hard work.