403 error with 2013ApJ...772..119L

[jonathansick]

This was brought up in #35 cc/@moustakas

prometheus:0.44% adsbibdesk --debug 2013ApJ...772..119L
Starting ADS to BibDesk
ADS to BibDesk version 3.2.dev
Python: 2.7.6 (default, Mar 12 2014, 06:23:30)
[GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.38)]
process_token found article token 2013ApJ...772..119L
ADSConnector found bibcode/DOI 2013ApJ...772..119L
ADSHTMLParser found links: {u'ar': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..19L&link_type=AR&db_key=AST
',
 u'article': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=ARTICLEdb_key=AST&high=
',
 u'bibtex': u'
http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2013ApJ...772..119L&data_type=BIBTEX&dbkey=AST&nocookieset=1
',
 u'citations': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=CITATONS&db_key=AST
',
 u'custom': u'
http://adsabs.harvard.edu/cgi-bin/nph-abs_connect?bibcode=2013ApJ...772..119L&data_type=Custom&ormat=%5c%5cbibitem%5b%25%5c2m%25%28y%29%5d%25%7bR%7d%20%25%5c5.3l%20%25%5cY,%25%5cj,%25%5cV,%25%5cp%5cn&retun_fmt=LONG&db_key=AST&nocookieset=1
',
 u'ejournal': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=EJOURNL&db_key=AST&high=
',
 u'preprint': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=PREPRIT&db_key=AST
',
 u'refcit': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=REFCIT&d_key=AST&high=
',
 u'references': u'
http://adsabs.harvard.edu/cgi-bin/nph-data_query?bibcode=2013ApJ...772..119L&link_type=REFEENCES&db_key=AST&high=
'}
Resolve article URL:
http://iopscience.iop.org/0004-637X/772/2/119/pdf/apj_772_2_119.pdf
http://iopscience.iop.org/0004-637X/772/2/119/pdf/apj_772_2_119.pdf failed:
HTTP Error 403: Forbidden
arXiv PDF (http://arXiv.org/pdf/1303.5059)

[jonathansick]

@moustakas This article worked for me. I’m thinking that the 403 might have been a random server hiccup with IOP. Does the problem persist for you still?

[paxperscientiam]

I was able successfully ingest this into bibdesk. Is it possible that permissions were temporarily incorrectly set on their end. I'm not sure, but I wonder if a 403 can occur when attempting to download a journal article from a network that doesn't have access to the journal's server. I know that in order to download some articles I must be logged into my uni's VPN.