@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.
Convenient. Can the sample endpoint (<a href="http://allorigins.pw/get?url=" rel="nofollow">http://allorigins.pw/get?url=</a>) be used by pages or do I need to deploy it myself?<p>How about CORS version instead of JSONP?
If I put the following in the "Try it yourself!" box:<p><a href="http://www.stockhouse.com/companies/bullboard/t.y/yellow-media-limited" rel="nofollow">http://www.stockhouse.com/companies/bullboard/t.y/yellow-med...</a><p>....should I be seeing anything in the "Example json output" box?
Interesting go-around to CORS.<p>There's a reason browser's have same-origin protections: to stop spammy behavior and protect against malintent by original or injected scripts.<p>This service will be fine for a bit, but once it's used for the above purposes, it'll end up in blocklists.