<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Access-Control on Digital Archive Systems Tech Blog</title><link>https://tech.ldas.jp/en/tags/access-control/</link><description>Recent content in Access-Control on Digital Archive Systems Tech Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 27 Apr 2026 22:00:00 +0900</lastBuildDate><atom:link href="https://tech.ldas.jp/en/tags/access-control/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Access-Controlled IIIF Digital Archive — Cantaloupe + S3 + Elasticsearch + Next.js, Gated by Cloudflare Access</title><link>https://tech.ldas.jp/en/posts/access-controlled-iiif-archive-cloudflare-cantaloupe/</link><pubDate>Mon, 27 Apr 2026 22:00:00 +0900</pubDate><guid>https://tech.ldas.jp/en/posts/access-controlled-iiif-archive-cloudflare-cantaloupe/</guid><description>&lt;blockquote>
&lt;p>This article is co-authored with a generative AI. Facts have been cross-checked against official documentation where possible, but errors may remain. Please verify against primary sources before making any important decisions.&lt;/p>&lt;/blockquote>
&lt;h2 id="background-we-need-to-deliver-iiif-for-images-we-cannot-publish-openly">Background: &amp;ldquo;We need to deliver IIIF for images we cannot publish openly&amp;rdquo;&lt;/h2>
&lt;p>Digital archives of historical materials almost always include a non-trivial slice of images that &lt;strong>cannot be released to the general public&lt;/strong> — for reasons of copyright, personality rights, contracts with the holding institution, or ethical considerations. At the same time, internal use cases such as&lt;/p></description></item></channel></rss>