Commit Graph

14 Commits (a5e3652d26ccf97ca321370fd2c020ed36855617)

Author SHA1 Message Date
Travis Ralston 6421582bf2 Clarifications and alter the error handling of .well-known
Note that MSC1831 changes the order, so the changes to MSC1708 might not make sense when combining all the proposals together. However, independently the change should make sense.
6 years ago
Richard van der Hoff de57d3950f
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.
6 years ago
Richard van der Hoff c10394d03f Clarifications thanks to @uhoreg 6 years ago
Richard van der Hoff b541c2a247 more formatting 6 years ago
Richard van der Hoff 5812450299 spec that we follow redirects 6 years ago
Richard van der Hoff f1ebbc358b document dismissed options 6 years ago
Richard van der Hoff fb171cadf4 formatting fix 6 years ago
Richard van der Hoff f33a540e6d Do a SRV lookup before .well-known lookup
also other clarifications and corrections.
6 years ago
Richard van der Hoff e789eb186a link to MSC1711 6 years ago
Matthew Hodgson b1e79ac7ab
Update 1708-well-known-for-federation.md 6 years ago
Richard van der Hoff 09d41464e7 Add problems section
xs
6 years ago
Richard van der Hoff c4e1949cf8 Clarifications about what `server` means 6 years ago
Richard van der Hoff e3f10a4fd2
Update 1708-well-known-for-federation.md
fix title
6 years ago
Richard van der Hoff 87330b9b9b Proposal for .well-known for server discovery 6 years ago