In native EZProxy, the concatenated-hostname syntax is what you get after you have logged in to EZProxy (assuming you're using the so-called "New Strategy", i.e. proxying by host name rather than by port). It's safer to initiate sessions using the "login?url=" syntax (starting point urls - see http://www.usefulutilities.com/support/cfg/database.html#spu). So, in the situation Ross describes, an external user should encounter only starting-point urls. But if III has changed this behavior then there won't be an automatic way to detect proxied links. Peter > -----Original Message----- > From: Code for Libraries [mailto:[log in to unmask]] On > Behalf Of Riesner, Giles > Sent: Wednesday, January 26, 2005 09:22 AM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolver list + Proxy > > I suspect Libraries are probably one of the primary users in > order to give access to database subscriptions to their > patrons from off-site. > > I know that the automated library system that we use (from > Innovative Interfaces, Inc. - out of Califormia) has licensed > EZ-proxy and has a slightly different syntax for their server > than the one shown below. > > In III's version of the proxy the syntax is: > > http://port_number-url_of_database.library_address/rest_of_url > > Here's an example: > > > http://0-search.epnet.com.library.yoursite.edu/login.asp?profi le=web&defaultdb=aph > > The "0" here is used to represent port 80, the default > port; if a different port > were used (e.g. 81) it would replace the 0. > > The URL for this resource without the proxy would be: > > http://search.epnet.com/login.asp?profile=web&defaultdb=aph > > > This could be useful for libraries if they don't want > internal users going through the proxy, though in III's > system at least you can set up "levels" for verification and > have all local IP addresses use IP verification with external > users authenticating. > > Otherwise, for external use, generally if you try the > unproxied versions of some of these URLs you're prompted for > a username and password, since they are licensed rather than > free materials. > > Giles W. Riesner Jr., Library Tech Support Community College > of Balto. Co. - Catonsville 800 S. Rolling Rd., Baltimore MD > 21228 USA > Tel/V-Mail 1-410-455-4245 > Email: [log in to unmask] > > > > -----Original Message----- > From: Code for Libraries [mailto:[log in to unmask]]On > Behalf Of Binkley, Peter > Sent: Tuesday, January 25, 2005 2:54 PM > To: [log in to unmask] > Subject: Re: [CODE4LIB] resolver list + Proxy > > > Interesting idea - you could have a bookmarklet look for the > typical ezproxy pattern "/login?url=" to identify ezproxied > urls and rewrite them ... > > Peter > > > -----Original Message----- > > From: Code for Libraries [mailto:[log in to unmask]] > On Behalf > > Of Ross Singer > > Sent: Tuesday, January 25, 2005 09:13 AM > > To: [log in to unmask] > > Subject: Re: [CODE4LIB] resolver list + Proxy > > > > I realize that this message is now "so '04", but something > similar to > > this with regards to proxy servers would also be incredibly useful. > > > > For instance, there's no reason that I shouldn't be able to > access the > > resources on: > > http://library.caltech.edu/collections/engineering/computer.htm > > or > > http://www.tamu.edu/pvamu/library/dblist.html > > if I'm there and already have access to the resource. > > > > It'd be simple enough to write a bookmarklet or extension > or something > > that changes: > > http://pv-ezproxy.tamu.edu:2048/login?url=http://muse.jhu.edu/ > > plweb-cgi/fastweb?searchform+muse > > to: > > http://www.library.gatech.edu:2048/login?url=http://muse.jhu.e > du/plweb-cgi/fastweb?searchform+muse > > > > Possibly making other instutions' research and subject guides more > > useful to other organizations. > > > > The key is knowing that > > http://pv-ezproxy.tamu.edu:2048/login? is a proxy server... > > > > What do you think? > > > > -Ross. > > > > Daniel Chudnov wrote: > > > > > For some stuff I'd like to try, and maybe for browser extension > > > authors, among others, it would be helpful to have at least > > one public > > > list of some public openurl resolvers. If you like, if you might > > > kindly add your resolver to the just-started list here: > > > > > > http://curtis.med.yale.edu/unalog-trac/wiki/OpenurlResolverTable > > > > > > ...it would be very helpful. > > > > > > Or, if there's already a list like this elsewhere, please > > let me know. > > > > > > Thanks, -Dan > > > > > >