From de57d3950f0fb1fe7b0a9d21877d5e699709df36 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Tue, 29 Jan 2019 14:46:27 +0000 Subject: [PATCH] Relax the requirement for a content-type on .well-known (#1824) The main reason for this is that Apache etc won't stick a content-type on by default, because they don't know it's JSON, so requiring it seems like it will require unnecessary hoop-humping for everyone who wants to use a .well-known. --- proposals/1708-well-known-for-federation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/1708-well-known-for-federation.md b/proposals/1708-well-known-for-federation.md index 8105a6381..d23c0e2ff 100644 --- a/proposals/1708-well-known-for-federation.md +++ b/proposals/1708-well-known-for-federation.md @@ -43,9 +43,9 @@ certificate validation, and following 30x redirects (being careful to avoid redirect loops). If the request does not return a 200, continue to step 4, otherwise: -The response must have a `Content-Type` of `application/json`, and must be -valid JSON which follows the structure documented below. Otherwise, the -request is aborted. +The response must be valid JSON which follows the structure documented +below. Otherwise, the request is aborted. It is NOT necessary for the response +to have a `Content-Type` of `application/json`. If the response is valid, the `m.server` property is parsed as `[:]`, and processed as follows: