[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
It turns out that it is necessary to have *.nlm.nih.gov as the entry in
forward table, rather than *.ncbi.nlm.nih.gov

I neglected to point out in my earlier email that it was the URL for our
library's linkout holdings that was not working, rather than the general URL
for PubMed.

The url for our library takes this form:
http://0-www.ncbi.nlm.nih.gov.innopac.lsuhsc.edu/entrez/query.fcgi?holding=l
sunolib

The proxy rewrite url breaks down with the query.fcgi?...unless the forward
table entry is as stated above.

Thanks to Dena Plaisted at the University of Arkansas for Medical Sciences
for providing me with correct information.


Bruce Abbott
LSUHSC Library 
433 Bolivar St.
New Orleans, LA 70112

babbot@xxxxxxxxxx
504-568-6103 (voice)
504-568-7718 (fax)

-----Original Message-----
From: Abbott, Bruce [mailto:babbot@xxxxxxxxxx] 
Sent: Thursday, September 04, 2003 9:48 AM
To: Innopac-L (innopac@xxxxxxxxxx)
Subject: WAM Proxy-rewrite and PubMed


We are trying to proxy PubMed in order to provide remote access to journals
linked in PubMed to publishers that we have in our WAM forward table.

With the configuration of the WAM table that I'm using I'm getting this
message:

CCgiCookie::CheckValidCookieField() [1] 

and I believe this error message comes from PubMed itself, rather than being
a WAM error message.

Does anyone have a working forward table configuration for PubMed that they
would be willing to share?