I'm thinking this may be the only solution. I will mention it to the vendor, Ryan, thanks!
--Dave ================== David Walker Library Web Services Manager California State University http://xerxes.calstate.edu ________________________________________ From: Code for Libraries [code4...@listserv.nd.edu] On Behalf Of Wick, Ryan [ryan.w...@oregonstate.edu] Sent: Tuesday, August 25, 2009 1:22 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] EzProxy and recaptcha reCAPTCHA keys are tied to a domain name by default, but they also offer global keys. From an admin page: If you wish to use your key across a large number of domains (e.g., if you are a hosting provider, OEM, etc.), select the global key option. You may want to use a descriptive domain name such as "global-key.mycompany.com" Ryan Wick Information Technology Consultant Special Collections Oregon State University Libraries http://osulibrary.oregonstate.edu/specialcollections -----Original Message----- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Walker, David Sent: Tuesday, August 25, 2009 12:34 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] EzProxy and recaptcha Casting a net far and wide on this, sorry. We're using EZproxy to proxy a website that also happens to have reCaptcha on it. I guess reCaptcha keys are tied to domain names, so when the Javascript is brought into the page via the <script /> tag, it sees that the page is 'proxy.example.edu' instead of 'www.vendorsite.com', and we end-up with an error from reCaptcha saying: This reCAPTCHA key isn't authorized for the given domain. That all makes sense. But can anyone fathom a workaround? --Dave ================== David Walker Library Web Services Manager California State University http://xerxes.calstate.edu