Issue with requests

Sebastien_Peres-Labo 2016-09-20 08:07:13 UTC #1

Hi there.

I had severe issues regarding the Request class.
I had to switch back to the “old” mechanism to avoid constant
redirections and page constantly redirecting & reloading.

In Request.php, lines to 146 to 154 (git master) :

    if (is_null(self::$request_class))
    {
        // new default to use egw_cache to store

requests

        // self::$request_class =

CLASS.’\Cache’;

        // old default to use request if mcrypt and gzcompress are

available and session if
not

        self::$request_class = check_load_extension('mcrypt') &&

function_exists(‘gzcompress’) &&
self::init_crypt() ? CLASS :
‘etemplate_request_session’;

How may i check/debug that my setup is compliant with the use of the new
default ?
What causes may prevent my setup to enable “egw_cache to store requests” ?
Is it safe so use the “old default” ?

–
S.PERES-LABOURDETTE

RalfBecker 2016-09-24 17:07:06 UTC #2

Hi Sébastien,

Hi there.

I had severe issues regarding the Request class.
I had to switch back to the “old” mechanism to avoid constant
redirections and page constantly redirecting & reloading.

What means constant, can you elaborate a bit more?

What do you use as cache (is displayed above Admin >> PHP Information)?
If you use APCu, how much memory does it use?

Ralf

In Request.php, lines to 146 to 154 (git master) :
    if (is_null(self::$request_class))
    {
        // new default to use egw_cache to store
requests
        // self::$request_class =
CLASS.’\Cache’;
        // old default to use request if mcrypt and gzcompress are
available and session if
not
        self::$request_class = check_load_extension('mcrypt') &&
function_exists(‘gzcompress’) &&
self::init_crypt() ? CLASS :
‘etemplate_request_session’;
    }
How may i check/debug that my setup is compliant with the use of the new
default ?
What causes may prevent my setup to enable “egw_cache to store requests” ?
Is it safe so use the “old default” ?

–
S.PERES-LABOURDETTE

–
Ralf Becker
EGroupware GmbH [www.egroupware.org]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 631 31657-0

Sebastien_Peres-Labo 2016-09-26 12:31:12 UTC #3

RalfBecker 2016-09-26 12:42:19 UTC #4

Hi Sebastian,

Hi Ralf,

Constantly means that each click on any common “clickable” area (as
folder names in webmail) results in dozens of “redirect=” jumps to
finally end in a dummy empty place.

Cache is definitely Apcu with the following runtime settings :

apc.coredump_unmap 0
apc.enable_cli 1
apc.enabled 1
apc.entries_hint 4096
apc.gc_ttl 3600
apc.mmap_file_mask
apc.preload_path
apc.serializer php
apc.shm_segments 1
apc.shm_size 32M

If you are not running PHP 7+ which native APCu interface, 32M will be
ignored as for APC it is to small.
You need to at least 64M to be recogniced and therefore used from
EGroupware as cache.

Ralf

apc.slam_defense 1
apc.smart 0
apc.ttl 0
apc.use_request_time 1
apc.writable /tmp

It uses 3.8 % actually (1.2M).

–
Sébastien

De : Ralf Becker mailto:rb@egroupware.org
Envoyé : sam. 24 sept. 2016 19:07:06 CEST (CEST +0200)
À : Egroupware Ml mailto:egroupware-users@lists.sourceforge.net
Objet : Re: [eGroupWare-users] Issue with requests
Hi Sébastien,

Hi there.

I had severe issues regarding the Request class.
I had to switch back to the “old” mechanism to avoid constant
redirections and page constantly redirecting & reloading.
What means constant, can you elaborate a bit more?

What do you use as cache (is displayed above Admin >> PHP Information)?
If you use APCu, how much memory does it use?

Ralf
In Request.php, lines to 146 to 154 (git master) :
    if (is_null(self::$request_class))
    {
        // new default to use egw_cache to store
requests
        // self::$request_class =
CLASS.’\Cache’;
        // old default to use request if mcrypt and gzcompress are
available and session if
not
        self::$request_class = check_load_extension('mcrypt') &&
function_exists(‘gzcompress’) &&
self::init_crypt() ? CLASS :
‘etemplate_request_session’;
    }
How may i check/debug that my setup is compliant with the use of the new
default ?
What causes may prevent my setup to enable “egw_cache to store requests” ?
Is it safe so use the “old default” ?

–
S.PERES-LABOURDETTE
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

Sebastien_Peres-Labo 2016-09-26 13:21:46 UTC #5