I did a little experimentation (telnetting to see the headers),
ReturnHeadersNoCache (which manually uses ns_write to produce the
headers) did not use util_WriteWithExtraOutputHeaders (which
ReturnHeaders do use) so if you set ns_conn outputheaders beforehand,
use of ReturnHeadersNoCache will ignore any additions to ns_conn. There
are functions that will automatically take into account additional
headers from ns_conn outputheaders, procedures like ns_return for
example. I remember the differences now :)
Bug? ReturnHeadersWithCookieNoCache is what www/curriculum/index.tcl
may have to use if it intends to send out a header with cookies but with
caching disabled. Would someone confirm this? Thanks.
