LogSPU "type of access"

In one of the examples on the documentation page for LogSPU, there is a variable %{ezproxy-spuaccess}i that is called "type of access", and it appears to have the values 'proxy', 'local', or 'unknown'.  These are unexplained.

I have two resources, ilarjournal.oxfordjournals.org and gerontologist.oxfordjournals.org.  There is no longer a stanza containing "oxfordjournals.org" anywhere in config.txt, so both should result in Needhost errors when used in starting point URLs.  However, the Gerontologist SPU resolves to https://academic.oup.com/gerontologist/issue while Ilarjournal results in a Needhost error.

I don't see any difference between the two resources, how they resolve to oup.com outside of Ezproxy, or the format of the SPUs within Ezproxy.  However, I do notice that in the SPU log, "type of access" for Gerontologist is 'proxy' while for Ilarjournal it is 'unknown'.

What would cause one resource to have 'unknown' as "type of access"?  What does that even mean?

thanks for any advice,
Karl

--
Karl Hiller
Computer Info Analyst
University of Cincinnati Libraries
513-556-6203




********************************************************************
If you wish to stop receiving messages from EZPROXY-L or otherwise amend your preferences,
you can do so <a href="https://www.oclc.org/forms/internet-subscription.en.html">here</a>.
Or email [email protected] including the relevant text below in the body of the email:
• To unsubscribe: "unsubscribe EZPROXY-L"
• To receive EZPROXY-L in digest form: "set EZPROXY-L digest"
• To set your options to no mail: "set EZPROXY-L nomail"
• To receive these messages in the future "set EZPROXY-L mail"
To contact the list owners directly please send your message to [email protected].
If you unsubscribe from EZPROXY-L, you will no longer be able to participate in any of its features, including the public forum.
To unsubscribe from all OCLC marketing email communications
(including all OCLC listervs, OCLC Connect emails, OCLC event notifications, product/service/cooperative updates and newsletters),
please email us at [email protected].