6.0.0-beta1
7/6/25

[#9315] Services cache is not issuing the correct headers
Summary Services cache is not issuing the correct headers
Queue Horde Base
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester goncalo.queiros (at) portugalmail (dot) net
Created 10/18/2010 (5375 days ago)
Due
Updated 10/20/2010 (5373 days ago)
Assigned 10/19/2010 (5374 days ago)
Resolved 10/20/2010 (5373 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
10/20/2010 10:42:25 AM Jan Schneider State ⇒ Resolved
 
10/20/2010 10:34:57 AM goncalo (dot) queiros (at) portugalmail (dot) net Comment #5 Reply to this comment
It works :-)
Try this.
10/19/2010 05:46:34 PM Michael Slusarz Comment #4
Assigned to Michael Slusarz
State ⇒ Feedback
Reply to this comment
Try this.
10/18/2010 02:26:41 PM goncalo (dot) queiros (at) portugalmail (dot) net Comment #2
New Attachment: cache.diff Download
Reply to this comment
Now the promised attachment :-)
10/18/2010 01:33:23 PM goncalo (dot) queiros (at) portugalmail (dot) net Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Services cache is not issuing the correct headers
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ Yes
State ⇒ Unconfirmed
Reply to this comment
Currently, files (javascript and css) served by services/cache.php are 
not getting the proper header, making them not cache-able by the 
browser.

The problem is that cache.php issues a Horde_Registry::appInit, that 
will then call the Registry constructor which in turn calls the 
Horde_Session construct, where the session is started and the headers 
are issued.
The problem is that the Horde_Session constructor is relying on the 
existence of the $registry->initParams['session_cache_limiter'] 
variable:

session_cache_limiter(is_null($registry->initParams['session_cache_limiter']) 
? $conf['session']['cache_limiter'] : 
$registry->initParams['session_cache_limiter']);

But this params are only setted before the Horde_Registry is called, 
thus the session_cache_limiter will only be called with the $conf 
variable which value is 'nocache'.

I did solve the problem, but i don't think this is the intended way, 
but i attach the patch anyway

Saved Queries