BriteSnow disables all caching

[Ueland]

We discovered a rather serious issue today.
It turns out that

1: Britesnow removes HTTP cache control headers that has been set pre-chain (for example by a filter running before Britesnow does)

2: Britesnow closes the connection to the browser, making it impossible to set/fix the http caching header after Britesnow, post-chain.

com/britesnow/snow/web/WebController.java:400:
res.setHeader("Cache-Control", "no-cache,no-store,max-age=0");

Then in line 405, same file:
rc.getWriter().close();

I suggest that Britesnow does not do this, it should be up to the web application stack to decide how caching is handled, not Britesnow. The result now is that nothing in our web application will get cached. Neither in Varnish(which we use to cache up the whole web application), or in the clients browers.

[jeremychone]

Ueland, thanks for the info. First, I would agree with your premiss, Snow should do the less possible and give the maximum control to the application. So, I really thing that these two issues need to be resolve.

On the other hand, I would like to have a reasonable set of default for most common cases.

Anyway, give me few days of thinking of couple of options to solve your issue, while providing a good default behavior.

[jeremychone]

@Ueland I am going to fix this one in the next few days. By when do you need it?

[Ueland]

We have compiled up a version our self that has fixes this issue so there is no hurry on our part.(But a fix eventually, would be nice of course)