Http Proxy issues

[matafagafo]

We have one problem with Squid proxy caching system.
   The documents are stored in the proxy cache, so when the documents are update in the repository, the users are still getting the old version of the document, because the old version is supplied by the proxy server.
    I know that I can disable the proxy cache, but it don't are a option.
    How can I configure Alfresco to instruct the proxy to don't cache the the repository files ?
    Thanks for your help.

[kevinr]

Fix applied ALFCOM-2195

[msevestre]

Hello

I'm running Alfresco Community v3.0.0 (Stable 1526) from a XP server.

Everything is running fine except what I guess to be a caching problem, as explained here…

Could someone explain me how to integrate the modifications explained in this thread in my Alfresco currently running in order to stop caching issues ?

Regards
Matthieu

[kevinr]

Alfresco Community 3.2 will be out shortly - first thing next week in theory - and it will have this fix and a lot more besides.

Cheers,

Kev

[msevestre]

Hi

OK… could upgrade be "dangerous" ? May I loose my own customization (language settinh, mail, web interface setup, etc..)… the less I modify  a currently running setup, the best I feel (I don't even speak about Alfresco down during working hours, what I don't want)

In fact just changing the class or the .jar file would be so nice for me ! Any way just to do this ?

Matt

[kevinr]

Well it's always worth testing on a backup test server first!

AFAIK the only area of customisation that has changed is Authentication and similar- see the new subsystems docs: http://wiki.alfresco.com/wiki/Alfresco_Subsystems
The web-client configuration has not changed, only a few additions.

Yes it is quite possible to get the source of Alfresco, modify it, rebuilt it and apply the patched .class file to your .jar. There are a few posts about doing exactly that around on the forums.

Cheers,

Kev

[msevestre]

Well it's always worth testing on a backup test server first!

Unfortunately, we do not have such server

AFAIK the only area of customisation that has changed is Authentication and similar- see the new subsystems docs: http://wiki.alfresco.com/wiki/Alfresco_Subsystems
The web-client configuration has not changed, only a few additions.

OK, but I gues sthat Alfresco Setup delete current files, then I'll need to redo everything.

Yes it is quite possible to get the source of Alfresco, modify it, rebuilt it and apply the patched .class file to your .jar. There are a few posts about doing exactly that around on the forums.

Then I need to look for this, I would prefer such a solution (I'll update to 3.2 later, when people with backup servers will have fully tested it). Any pointer to this ?

Regards
Matt