Michael Davidson
2014-10-22 17:04:33 UTC
I know the EZ Proxy manual says not to use XDebug unless requested by OCLC support. Still, it would be immensely useful at times to have control over the info that gets stored in messages.txt.
For example, this week I've had reports from a few users that they were receiving logup.htm. I wanted to up the log level to capture things like usernames, groups, and the CAS authentication response. I can twiddle blindly with XDebug, but I could just end up accruing massive logs that still don't have the info I'm looking for.
Are the XDebug values documented anywhere, or is there an alternate way of getting such info out of EZ Proxy?
Thank you,
Mike
--
Michael Davidson, MLIS
Assistant Professor, Web Services Librarian
Lamson Library
Plymouth State University
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu
For example, this week I've had reports from a few users that they were receiving logup.htm. I wanted to up the log level to capture things like usernames, groups, and the CAS authentication response. I can twiddle blindly with XDebug, but I could just end up accruing massive logs that still don't have the info I'm looking for.
Are the XDebug values documented anywhere, or is there an alternate way of getting such info out of EZ Proxy?
Thank you,
Mike
--
Michael Davidson, MLIS
Assistant Professor, Web Services Librarian
Lamson Library
Plymouth State University
---
You are currently subscribed to ezproxy as: gee-***@m.gmane.org.
To unsubscribe, send request to ***@itec.suny.edu