trunk sends the deprecation INFO message when setting Cache-control via the 
addAdditionalHeaders hack. 

The Cache-control header setting is important for trying to interoperate with 
certain browsers. 

I searched but did not find any traffic on the planned means for supporting it. 
I'd love to try to contribute bits to land this one item in 1.1 if somebody can 
point me to the right guidance on how Restlet should support it. I have always 
treated this as an explicit setting made by code, never intuited by other 
behavior, so a simple setCacheControl(Message.CACHE_CONTROL_NO_CACHE) or 
something like that would do for my purposes ... but happy to run down the road 
of something more elegant if someone's already thunk it up. 

- Rob 

Reply via email to