Joel, it is completely harmless, as the user_id is being added to the
incoming HTTP headers not any outgoing headers. Yes, it
sounds odd, but that is actually the way it works. And no, adding the
extra data to the access log shouldn't break anything trying to read
it.
Here are yet three more threads dicussing this issue:
Nov. 2001,
May 2002,
April 2003.
As I
mentioned
back in 2002, it is easy to write the OpenACS user_id to the AOLserver
access log on each and every hit. However, when an error occurs, it
would be really nice if the user_id was included with the error stack
trace in the error log, but there is no obvious way to do this.
Has anyone since come up with a way to log the user_id to the error
log whenever a page throws a Tcl error?