Just a thought... why does this restriction exist in the first place?
Because, a long time ago, queries contained mostly user-defined strings that were not likely to result in a later hit, so it wasn't worth the effort. Now, some web applications use a bogus query string in order to override caching because of this default behavior.
It would be fine with me to change the default, but that may result in very inefficient caches. It is better to default to no-cache unless it is specifically configured or indicated (cache-control) as cacheable.
....Roy
