Thu, 12 Mar 2015 12:26:46 +0100 Added tag cubicweb-version-3.19.10, cubicweb-debian-version-3.19.10-1, cubicweb-centos-version-3.19.10-1 for changeset 3bab0b9b0ee7
Rémi Cardona <remi.cardona@logilab.fr> [Thu, 12 Mar 2015 12:26:46 +0100] rev 10227
Added tag cubicweb-version-3.19.10, cubicweb-debian-version-3.19.10-1, cubicweb-centos-version-3.19.10-1 for changeset 3bab0b9b0ee7
Thu, 12 Mar 2015 11:52:18 +0100 [pkg] 3.19.10 3.19.10 centos/3.19.10-1 cubicweb-centos-version-3.19.10-1 cubicweb-debian-version-3.19.10-1 cubicweb-version-3.19.10 debian/3.19.10-1
Rémi Cardona <remi.cardona@logilab.fr> [Thu, 12 Mar 2015 11:52:18 +0100] rev 10226
[pkg] 3.19.10
Thu, 12 Mar 2015 11:00:57 +0100 [i18n] Update translations
Rémi Cardona <remi.cardona@logilab.fr> [Thu, 12 Mar 2015 11:00:57 +0100] rev 10225
[i18n] Update translations Related to #5012581.
Wed, 11 Mar 2015 15:17:25 +0100 [config] Lowercase the FQDN we get from the OS (closes #5040345)
Rémi Cardona <remi.cardona@logilab.fr> [Wed, 11 Mar 2015 15:17:25 +0100] rev 10224
[config] Lowercase the FQDN we get from the OS (closes #5040345) Browsers convert the host name part of URLs to lowercase. This has the unfortunate effect of triggering various CORS error messages in CubicWeb (because the Origin: header will contain lowercase letters). As per RFC 4343, host name comparison should be case-insensitive. So let's put it in lowercase when we grab it from the host system. If admins put uppercase letters in "host" or "base-url" in their all-in-one.conf, then it's their fault.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 tip