> Geoff: I think I did this with my own module with no success... I'd end > up with an extra set of headers, if I was _lucky_...
perhaps that is due to a general misunderstanding of err_headers_out - they are sent _even_ on Apache errors (of which REDIRECT is considered one), not _only_ on errors. so, if you were setting headers_out to capture normal transactions and err_headers_out for errors, you might get an extra set of headers if you were not careful in your own coding methodology. > Also, when I got > it to redirect OK, even when I saw the cookie, sometimes the browser > would not eat the cookie properly... I don't have more specific > details, because this was months ago and the project was not (then) > under CVS control (now it is, of course)... well, details are good :) this sounds like a browser issue, though - if you populate the err_headers_out table with a cookie it will be presented to the client on a REDIRECT response. nevertheless, Axel emailed me privately saying that err_headers_out() solved his issues. --Geoff
