While poking around mime headers, I noticed we have a special case around this
internal header, @WWW-Auth. If set, it seems it can force cached content to be
reauthenticated on every request. This is handled by setting the
t_state.www_auth_content when this header is there.
Now, there’s nothing
I’d like to add this new TS API:
/**
Check to see if an MBuffer is still valid, from since the time
it was acquired.
*/
bool TSMBufferIsValid(TSMBuffer bufp);
The intent of this API is to check if a TSMbuffer, and any pointers related to
this buffer, are still valid. Why would they not b
