Hi Tom,
Indeed - if I just visit the URL with my browser, I'm getting the JSON just fine, with Access-Control-Allow-Origin:*. So this sounds as if we fall into the bot-blocking rule. The request sent by the Widget sample page is this:
Request URL:
http://pleiades.stoa.org/places/579885/json
Request Headers
POST
http://pleiades.stoa.org/places/579885/json HTTP/1.1
Accept: application/json, text/javascript, */*; q=0.01
Referer:
http://pelagios.github.io/pelagios-widgets/
Origin:
http://pelagios.github.io
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
Cheers,
Rainer
________________________________________
Von: Tom Elliott [
tom.e...@nyu.edu]
Gesendet: Freitag, 13. Dezember 2013 15:56
An: Simon Rainer
Cc:
pelagios...@googlegroups.com; Fasti Support
Betreff: Re: [pelagios] Pelagios Widget not working
Rainer:
I think the error message you’re seeing may be masking a different issue. I am seeing Access-Control-Allow-Origin: * in response to a request for the URL you mentioned. Viz:
dark-star:Downloads paregorios$ curl -I
http://pleiades.stoa.org/places/579885/json
HTTP/1.1 200 OK
Date: Fri, 13 Dec 2013 14:52:20 GMT
Server: nginx/1.0.15
Content-Type: application/json
Access-Control-Allow-Origin: *
Content-Length: 4507
X-Varnish: 1566988539
Age: 0
Via: 1.1 varnish
Via: 1.1
pleiades.stoa.org<
http://pleiades.stoa.org>
Cache-Control: max-age=86400, s-maxage=11988
Expires: Sat, 14 Dec 2013 14:52:18 GMT
Can you send me a dump of the full request, with headers, that’s throwing the error on your end? I may be inadvertently blocking you as a bot; we serve a 403 to requests for json resources that we think are coming from search bots and bad actors. We may need to tweak the rules to let pelagios traffic through.
Sorry for the hassle.
Thanks,
Tom
Tom Elliott, Ph.D.
Associate Director for Digital Programs and Senior Research Scholar
Institute for the Study of the Ancient World (NYU)
http://isaw.nyu.edu/people/staff/tom-elliott
XMLHttpRequest cannot load
http://pleiades.stoa.org/places/579885/json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '
http://pelagios.github.io<
http://pelagios.github.io/>' is therefore not allowed access.
which means cross-origin (CORS) requests are no longer possible on the Pleiades server.
@Tom: do you have any time to look into the issue? Seems that the CORS server setting (i.e. the header additional “Access-Control-Allow-Origin” response header, set to “*”) that used to be there has gone lost :-(
Cheers & thanks,
Rainer
j.o...@lparchaeology.com<mailto:
j.o...@lparchaeology.com>
Digital Consultant, Geophysical Specialist
Tel: 020 7770 6045
The Old Truman Brewery, 91 Brick Lane, London E1 6QL
Chester: 01244 313 100 East of England: 01284 754 859 Marches: 01938 559 610
WWW.LPARCHAEOLOGY.COM<
http://www.lparchaeology.com/>
IfA Registered Archaeological Organisation
***************************************************
L - P : Archaeology is the trading name of L - P : Heritage LLP Registered in England and Wales OC366545
Registered office address: Amelia House, Crescent Road, Worthing, BN11 1QR
--
You received this message because you are subscribed to the Google Groups "pelagios" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
pelagios-proje...@googlegroups.com<mailto:
pelagios-proje...@googlegroups.com>.