<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Hosting a local proxy to deal w/ CORS]]></title><description><![CDATA[<p dir="auto">Has anyone dealt w/ trying to get data from an API that has CORS disabled?  I expect that you can deal w/ it simply by running a proxy w/in the webserver.  Maybe using something like this? <a href="https://www.npmjs.com/package/cors-anywhere" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.npmjs.com/package/cors-anywhere</a></p>
<p dir="auto">Curious if this is a problem that’s already been solved though.</p>
]]></description><link>https://forum.magicmirror.builders/topic/4171/hosting-a-local-proxy-to-deal-w-cors</link><generator>RSS for Node</generator><lastBuildDate>Mon, 17 Aug 2026 08:17:45 GMT</lastBuildDate><atom:link href="https://forum.magicmirror.builders/topic/4171.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 19 Jun 2017 13:34:08 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Hosting a local proxy to deal w/ CORS on Tue, 20 Jun 2017 02:42:37 GMT]]></title><description><![CDATA[<p dir="auto">Nevermind.  I get it now.  Node helper is the way around this problem.  I’m all set.</p>
]]></description><link>https://forum.magicmirror.builders/post/24278</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/24278</guid><dc:creator><![CDATA[trasnportGuy]]></dc:creator><pubDate>Tue, 20 Jun 2017 02:42:37 GMT</pubDate></item></channel></rss>