Show HN: AllOrigins – Pull content from any page as JSON via API (allorigins.pw) 46 points by hezag 10y ago ↗ HN
[–] jerluc 10y ago ↗ @OP: FYI I'm getting mixed content errors with the example fetch because the AllOrigins page itself is served over HTTPS, but the backend call is going to HTTP. May be a good idea to swap that out. [–] hezag 10y ago ↗ Fixed, thanks for pointing it out!
[–] prohor 10y ago ↗ Convenient. Can the sample endpoint (http://allorigins.pw/get?url=) be used by pages or do I need to deploy it myself?How about CORS version instead of JSONP? [–] hezag 10y ago ↗ A CORS version is planned! And yes, you can use the sample endpoint in your pages.
[–] hezag 10y ago ↗ A CORS version is planned! And yes, you can use the sample endpoint in your pages.
[–] mistermann 10y ago ↗ If I put the following in the "Try it yourself!" box:http://www.stockhouse.com/companies/bullboard/t.y/yellow-med.......should I be seeing anything in the "Example json output" box? [–] hezag 10y ago ↗ Yep http://i.imgur.com/nwMgL4o.jpg
[–] anilgulecha 10y ago ↗ Interesting go-around to CORS.There's a reason browser's have same-origin protections: to stop spammy behavior and protect against malintent by original or injected scripts.This service will be fine for a bit, but once it's used for the above purposes, it'll end up in blocklists.
8 comments
[ 5.4 ms ] story [ 32.6 ms ] threadHow about CORS version instead of JSONP?
http://www.stockhouse.com/companies/bullboard/t.y/yellow-med...
....should I be seeing anything in the "Example json output" box?
There's a reason browser's have same-origin protections: to stop spammy behavior and protect against malintent by original or injected scripts.
This service will be fine for a bit, but once it's used for the above purposes, it'll end up in blocklists.