Closed osnet closed 3 years ago
ah lol wait ... i had mounted my configs manually so they werent generated as they are now ... i guess i have to apply the docker.unlock thingy i'll have a try tomorrow
i was right
apologize .. with docker unlock stuf all ne settings got applied, yes but the configfile app-conf/webapp/config.php did not get changed
@osnet
Yes, the switch from define("INSECURE_COOKIES", true);
to define("SECURE_COOKIES", false);
was introduced in WebApp 5.0.0, see Kopano WebApp HTTP access.
To help with migrating older configurations I introduced in 230e6953fd436b529b454fb292df7320858a58e2 MIGRATE_CONFIG=all
, see MIGRATE_CONFIG=1 Rejected insecure request as configuration for SECURE_COOKIES is true.
Mark as closed.
Hi, i know i have a different volume setup than you .. but i have encountered a lil bug : )
i thought with spinning up the new docker image revision it will overwrite its old configfiles.
ERRRRR, not as expected
in
app-conf/webapp/config.php
we have a value Line 45define("INSECURE_COOKIES", true);
After spinning up the stuff i got Error400 in my borwsers. Docker exec-it .... curl 127.0.0.1:80 same thing.
Playing round with apache2 errorlogging within the container i got
According to kopano.io we have to change our config.php
just switch from
define("INSECURE_COOKIES", true);
todefine("SECURE_COOKIES", false);
restart the containers
all fine again...
can you confirm this in some way ? or is this just me : PP