I appreciate the replies. I realize it was mostly on a specific topic that
is handled elsewhere, I also thought it was a more general wildcard SSL
topic that would be of interest to the C4L community.
But the replies helped--as did my limited experience in the different
realms of the problem, the C4L archives, EZproxy list archives, EZproxy
docs, educated google searches, uneducated google searches, cosmic
ray-induced inspiration, appeals to various deities, and the statistical
likelihood of typing in sorta the right commands until nothing broke. I
think you can't predict what sort of documentation actually works. E-mail
lists are timely for the person asking but noisy and repetitive for
everyone else. Wikis are written by the learned for the unlearned and will
always be difficult for the latter. Listserv archives are about the same,
maybe better if you want outdated information or if you prefer search
interfaces that never really work. So, I think the more documentation the
better. Often you don't learn things in one blast, but with lots of little
On Wed, Feb 17, 2016 at 4:40 PM, Salazar, Christina <
[log in to unmask]> wrote:
> Well, you told me ;-) Or let me say, I get it and I’m glad we had this
> talk. Thx.
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Gorman, Jon
> Sent: Wednesday, February 17, 2016 12:43 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] SSL certificates and proxy servers
> > I want to make a plea too, not to fragment Code4Lib, but rather to
> > consolidate EZProxy knowledge to post these queries to the EZProxy list.
> > For good, bad or indifferent, OCLC is putting together an EZProxy
> > community wiki and for those EZProxy folks who come after you, who are
> > not C4Lers, I ask that whatever info go there.
> If we're going to go that far, why not also put it in the existing system?
> Honestly, I'm expecting much from the wiki. I tried using the community
> resource as it is now in the past and have had errors, things disappearing,
> etc. I think I may have put something up in the community site, but
> honestly, I'm probably never going to log in again if I don't have to. A
> lot of it is simply poor management and needless restrictions, which will
> be the same no matter what software they use.
> This particular question is definitely a FAQ and someday I'll get around
> to trying to write up something and I'll put it up ..somewhere. Maybe even
> just up in github and send it to the link.
> I don't see the harm in repeating info here. I'm guessing folks who find
> this new information aren't already on ezproxy and won't be on there.
> They're not likely to find it either, the ezproxy-l list doesn't seem very
> well exposed to searching.
> > (@Jon, kind of looking at you because I worry that EZProxy expertise
> > such as yours will get lost. I know it seems impossible, but one day
> > we may all go on to other work. I for one am looking forward to an
> > exciting second career as a Starbucks barrista; I hear my Master's
> > degree will serve me well there ;-)
> I'm guessing no matter where or how I put the information, people will
> still ask the questions :). My learned knowledge about ezproxy is combined
> a bit from the mailing list, a large part in just reading the OCLC
> documentation, and a little from ./ezproxy --help or whatever it is :).
> I'll try to dump some of the info or create an FAQ one of these days, but
> it probably won't be today.
> Or, of course, someone else could visit
> http://search.gmane.org/?query=wildcard&group=gmane.education.ezproxy and
> type in the search box wildcard and summarize the various emails on the
> topic ;).
> Jon Gorman
> Library IT
> University of Illinois
> 217 244-4688