<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #cors</title>
    <link>/tags/cors/</link>
    <description>Recent bookmarks tagged #cors</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:52 +0000</lastBuildDate>
    <item>
      <title>Enabling CORS in Synology WebDav</title>
      <link>https://github.com/keeweb/keeweb/issues/703#issuecomment-326404286</link>
      <description>ssh ip-synology&#xD;&#xA;cd /var/packages/WebDAVServer/target/etc/httpd/&#xD;&#xA;sudo vim conf/httpd.conf-webdav add&#xD;&#xA;   LoadModule rewrite_module modules/mod_rewrite.so&#xD;&#xA;sudo vim conf/extra/httpd-ssl.conf-webdav add :&#xD;&#xA;   Header always set Access-Control-Allow-Origin &#34;*&#34;&#xD;&#xA;   Header always set Access-Control-Allow-Headers &#34;origin, content-type, cache-control, accept, authorization, if-match, destination, overwrite&#34;&#xD;&#xA;   Header always set Access-Control-Expose-Headers &#34;ETag&#34;&#xD;&#xA;   Header always set Access-Control-Allow-Methods &#34;GET, HEAD, POST, PUT, OPTIONS, MOVE, DELETE, COPY, LOCK, UNLOCK&#34;&#xD;&#xA;   Header always set Access-Control-Allow-Credentials &#34;true&#34;&#xD;&#xA;&#xD;&#xA;   RewriteEngine on&#xD;&#xA;   RewriteCond %{REQUEST_METHOD} OPTIONS&#xD;&#xA;   RewriteRule ^(.*)$ blank.html [R=200,L,E=HTTP_ORIGIN:%{HTTP:ORIGIN}]&#xD;&#xA;&#xD;&#xA;cd /var/packages/WebDAVServer/target/tools&#xD;&#xA;sudo ./start_stop.sh start restart&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #cors #imported:pinboard #synology #webdav #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 26 Dec 2018 20:02:23 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:27997</guid>
      <category>cors</category>
      <category>imported:pinboard</category>
      <category>synology</category>
      <category>webdav</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Enabling Cross-Origin Resource Sharing - Amazon Simple Storage Service</title>
      <link>http://docs.amazonwebservices.com/AmazonS3/latest/dev/cors.html</link>
      <description>Cross-origin resource sharing (CORS) defines a way for client web applications that are loaded in one domain to interact with resources in a different domain. With CORS support in Amazon S3, you can build rich client-side web applications with Amazon S3 and selectively allow cross-origin access to your Amazon S3 resources.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #amazon #cors #imported:pinboard #s3 #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 01 Sep 2012 14:45:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:22509</guid>
      <category>amazon</category>
      <category>cors</category>
      <category>imported:pinboard</category>
      <category>s3</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The Imgur API - Examples</title>
      <link>http://api.imgur.com/examples</link>
      <description>Uploading - HTML5 Canvas&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #canvas #cors #html5 #images #imgur #imported:pinboard #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 16 May 2012 01:58:52 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21772</guid>
      <category>canvas</category>
      <category>cors</category>
      <category>html5</category>
      <category>images</category>
      <category>imgur</category>
      <category>imported:pinboard</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Cross-domain Ajax with Cross-Origin Resource Sharing | NCZOnline</title>
      <link>http://www.nczonline.net/blog/2010/05/25/cross-domain-ajax-with-cross-origin-resource-sharing</link>
      <description>&#34;A couple of years ago, web developers were banging their head against the first wall in Ajax: the same-origin policy. While we marveled at the giant step forward enabled by cross-browser support for the XMLHttpRequest object, we quickly bemoaned the fact that there was no way to make a request to a different domain from JavaScript. Everyone setup proxies on their web sites, which was the onset of a new host of open redirect problems, as a way to get around the restriction. Although developers were working around this limitation using server-side proxies as well as other techniques, the community outcry was around allowing native cross-domain Ajax requests. A lot of people are unaware that almost all browsers (Internet Explorer 8+, Firefox 3.5+, Safari 4+, and Chrome) presently support cross-domain Ajax via a protocol called Cross-Origin Resource Sharing.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ajax #cors #crossdomain #security #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 13 Jul 2010 18:29:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:13743</guid>
      <category>ajax</category>
      <category>cors</category>
      <category>crossdomain</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
