On 12-05-24 3:06 PM, Peter Peltonen wrote:

On Thu, May 24, 2012 at 9:34 PM, Jean Raby<jr...@inverse.ca>  wrote:
We could finally reproduce the issue and it should now be fixed in the
nightly builds (sope).

Will there be 1.3.15b or should one install 1.3.15a + updated sope
packages from nightly? And which of the sope packages should be

The fix is in sope49-appserver, nothing changed in sogo regarding this issue.

And is the nightly version 20120524 or 20120525 where this is fixed?

It will be in 20120525 (tomorrow).

The default apache configuration has been updated to allow the caching:

<Directory /usr/lib/GNUstep/SOGo/>
    AllowOverride None
    Order deny,allow
    Allow from all

    # Explicitly allow caching of static content to avoid browser specific
    # A resource's URL MUST change in order to have the client load the new
    <IfModule expires_module>
      ExpiresActive On
      ExpiresDefault "access plus 1 year"

And when updating should one add these changes to the Apache configs manually?

Since this is a configuration file, yes, it should be changed manually.

Jean Raby
jr...@inverse.ca  ::  +1.514.447.4918 (x120) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)

Reply via email to