Protocol Transition fails and the user gets a 401 unauthorized message
Protocol Transition does not work. User receives a 401 message in the browser.
The ct_agent.log shows a 401 error message indicating the the content cannot be served with the current credentials.
2009-05-27 15:53:36 -0400 - [1672] - <Debug> - AUTH_TYPE: Basic
2009-05-27 15:53:36 -0400 - [1672] - <Info> - [NotifyAccessDenied]
2009-05-27 15:53:36 -0400 - [1672] - <Debug> - REMOTE_USER:
2009-05-27 15:53:36 -0400 - [1672] - <Debug> - LOGON_USER:
2009-05-27 15:53:36 -0400 - [1672] - <Debug> - AUTH_TYPE:Basic
2009-05-27 15:53:36 -0400 - [1672] - <Info> - [NotifySendResponse]
2009-05-27 15:53:36 -0400 - [1672] - <Debug> - Response: 401
The following messages do NOT appear in the ct_agent.log file. The absence fo the "WildCard map extension loaded" suggests a problem with the wildcard map.
2008-04-29 13:46:25 -0700 - [2284] - <Debug> - Windows user token cache initialized, size : 3000, ttl:28800
2008-04-29 13:46:25 -0700 - [2284] - <Info> - Domain name: SUPPORTLAB7
2008-04-29 13:46:25 -0700 - [2284] - <Info> - WildCard map extension loaded
The ct_tokengen.log shows startup information but there is no other messages in the log files.