K Khan
OMVPPaaS CMS Administrator Certification
Jan 15, 2024
visibility 8143
star star star star star star
(2 votes)

Toptip - what is .well-known folder

Within your ~/public folder, you may come across a directory named ".well-known." This directory is frequently employed in web-based protocols to retrieve "site-wide metadata" related to a host before initiating a request. It's important to note that the absence of this folder doesn't necessarily indicate an issue; it simply means it hasn't been utilized or generated yet.

Here are some examples of what you might find in the ".well-known" directory:

  1. .well-known/security.txt: Contains information about a website's security policies and contact information for security researchers.
    Please read some helpful blogs on this topic.
    https://www.gulla.net/en/blog/security.txt
    https://optimizely.blog/2023/03/easy-implementation-of-security.txt-with-minimal-api-.net-core
  2. .well-known/apple-app-site-association (AASA): Used for associating iOS apps with websites, enabling features like Universal Links. This file doesn't have an extension.

  3. .well-known/assetlinks.json: Used in the context of Android App Links. Android App Links are a way to associate a website with a specific Android app, allowing the app to open when certain links are clicked, even if the app is not currently installed on the device.
Jan 15, 2024

Comments

Scott Reed
Scott Reed Jan 15, 2024 01:25 PM

I'll be honest it wasn't very clear to me that the link on security.txt was a link to another blog post that covered it in more detail, can you make that clearer.

Also (and I mentioned this on Tomas's blog) it might be worth a link to as well to https://optimizely.blog/2023/03/easy-implementation-of-security.txt-with-minimal-api-.net-core too as there's some more code exmples and explanation on the security.txt

K Khan
K Khan Jan 15, 2024 01:38 PM

Thanks for the feedback, I have updated the contents.

Scott Reed
Scott Reed Jan 15, 2024 05:49 PM

Super, great work :-)

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026