Richfaces 4.2.2 Final / CCS and Javascript expires header

javacoryd Jan 8, 2014 4:53 PM

Hello,

We have migrated our applications to Richfaces 4 and I'm getting a bunch of "Not-Modified" responses in our access logs on Richfaces CCS and Javascript files. Is there any way I can set the expires headers on these resources?

Thanks!

Cory.

1. Re: Richfaces 4.2.2 Final / CCS and Javascript expires header

lfryc Jan 20, 2014 12:35 PM (in response to javacoryd)

You can definitely setup a WebFilter that will add relevant headers.
Actions
2. Re: Richfaces 4.2.2 Final / CCS and Javascript expires header

suckerd Jan 24, 2014 9:54 AM (in response to lfryc)

Yeah, good point, but in richfaces 3.3.x there used to be a context-parameter org.ajax4jsf.DEFAULT_EXPIRE for handling those issues.
Would be great to have the same functionality back - otherwise everybody has to implement his own resource filter ...
Actions
3. Re: Richfaces 4.2.2 Final / CCS and Javascript expires header

lfryc Feb 10, 2014 6:56 AM (in response to suckerd)

Hey guys,

we need to know which resources cause you troubles and from where they come from
in order to identify what is an issue and from which subsystem it comes.
Actions

Go to original post