General discussion on installation and configuration of SOGo

Text archives Help


Re: Browser cache and upgrades (Was: Re: [SOGo] ANN: SOGo v1.3.15)


Chronological Thread 
  • From: Jean Raby < >
  • To:
  • Subject: Re: Browser cache and upgrades (Was: Re: [SOGo] ANN: SOGo v1.3.15)
  • Date: Thu, 24 May 2012 15:19:54 -0400

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

On Thu, May 24, 2012 at 9:34 PM, Jean
Raby< >
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
updated:

sope49-appserver
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
behavior.
# A resource's URL MUST change in order to have the client load the new
version.
<IfModule expires_module>
ExpiresActive On
ExpiresDefault "access plus 1 year"
</IfModule>
</Directory>

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.
Regards,
Peter


--
Jean Raby

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



Archive powered by MHonArc 2.6.18.

Top of page