<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>htaccess &#8211; Business Legions Blog</title>
	<atom:link href="https://www.businesslegions.com/blog/tag/htaccess/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.businesslegions.com/blog</link>
	<description>Deals, entrepreneur, money, business, website, design,technology and random ramblings</description>
	<lastBuildDate>Wed, 11 May 2016 09:01:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>RESOLVING ISSUE WITH CROSS ORIGIN RESOURCE SHARING POLICY FOR WEBSITES</title>
		<link>https://www.businesslegions.com/blog/2016/05/12/resolving-issue-with-cross-origin-resource-sharing-policy-websites/</link>
					<comments>https://www.businesslegions.com/blog/2016/05/12/resolving-issue-with-cross-origin-resource-sharing-policy-websites/#respond</comments>
		
		<dc:creator><![CDATA[Marco]]></dc:creator>
		<pubDate>Wed, 11 May 2016 15:50:38 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[Websites]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[cross]]></category>
		<category><![CDATA[curl]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[origin]]></category>
		<guid isPermaLink="false">https://www.businesslegions.com/blog/?p=5064</guid>

					<description><![CDATA[<input type="hidden" id="_wpnonce" name="_wpnonce" value="253821b87a" /><input type="hidden" name="_wp_http_referer" value="/blog/tag/htaccess/feed/" />Another issue that we experienced was displaying content from different domains especially when using HTTP and HTTPS. Here&#8217;s an example of the error message: Font from origin &#8216;https://website&#8217; has been blocked from loading by Cross-Origin Resource Sharing policy: No &#8216;Access-Control-Allow-Origin&#8217; header is present on the requested resource. Origin &#8216;http://website&#8217; is therefore not allowed access. The [&#8230;]]]></description>
		
					<wfw:commentRss>https://www.businesslegions.com/blog/2016/05/12/resolving-issue-with-cross-origin-resource-sharing-policy-websites/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
