To set headers, just use ns_set update [ns_conn outputheaders] Header Value.
All of the ns_return flavors will then return the headers to the user. You
shouldn't have to mess with ns_respond at all.
Jim
> > 2a. this assumes that you include the aforementioned outputheaders in the
> > request. note that ns_returnredirect doesn't allow for a -headers
> > arguement. we instead use a wrapper around ns_respond, which isn't as bad
> > as it first seems.
>
> heh, first I have looked at ns_respond... now I have to figure out how to
> handle headers.. :)
>
> > 2b. there was a bug a while back i noted but never took the time to
> > duplicate, about ns_conn outputheaders not working. it might be part of
> > your problem. do a search of the archives for the string "TCL_OUTHDRS" or
> > "ns_conn outputheaders does not work" and you'll probably hit the bug i'm
> > talking about.
>
> might be..
>
> > i think in general you'll want to switch to using ns_respond and setting
> > your own outputheaders, but ns_returnredirect should pass along the
> correct
> > headers- i.e. including the ones you've set.
>
> it hasn't so far for me :) but I should have this all straightened out and
> finished this weekend (hope hope hope) then I can write up my trials and
> tribulations of getting the ccBill credit card charging system to work with
> Aolserver.. (I had to *shudder* call tcl scripts from perl scripts)....
>
> >
> > folks, is this last assumption correct?
> >
>
> --
> Patrick Spence <[EMAIL PROTECTED]>
> Want weather reports delevered to your desktop?
> http://ww2.weatherbug.com/aff/default.asp?ZCode=z3345
>
