Thanks, Eric. I can give those a shot. Some info is better than nothing.
Head of Library Systems & Technology (Librarian III)
Miller Nichols Library
University of Missouri--Kansas City
From: Code for Libraries <[log in to unmask]> On Behalf Of Eric Phetteplace
Sent: Thursday, November 15, 2018 2:43 PM
To: [log in to unmask]
Subject: [BEWARE-SUSPECTED SPAM]Re: [CODE4LIB] Capturing referring URL for proxy problem?
Browser support is bad (Chrome & Firefox only <https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer#Browser_compatibility>).
In my testing, document.referrer only returns the google domain, not a full URI, for search referrals and was sometimes entirely empty (e.g. after going through our CAS login screen on the way through EZproxy). Good luck!
On Thu, Nov 15, 2018 at 12:29 PM Pennington, Buddy D. <[log in to unmask]>
> Hi all,
> We are an EZproxy shop. If someone clicks a proxied link and gets
> directed to the needhost.html error page because the proxied link is
> not included in the configuration file we collect that link and allow
> the user to submit the problem to us to fix. What we would also like
> to collect is the page the user is on when they click the problem
> link. For example, if they click a bad EBSCO link on a Canvas page, we
> want to collect both the EBSCO link and the Canvas page URL. Is there a fairly easy way to do this?
> Buddy Pennington
> Head of Library Systems & Technology (Librarian III) Miller Nichols
> Library University of Missouri--Kansas City