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.
2019-02-01 08:18:12 -07:00
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.
2019-01-29 14:46:27 +00:00
c10394d03f
Clarifications thanks to @uhoreg
2019-01-09 11:26:14 +00:00
b541c2a247
more formatting
2019-01-08 12:54:52 +00:00
5812450299
spec that we follow redirects
2019-01-08 12:51:23 +00:00
f1ebbc358b
document dismissed options
2019-01-08 12:51:23 +00:00
fb171cadf4
formatting fix
2019-01-08 12:51:23 +00:00
f33a540e6d
Do a SRV lookup before .well-known lookup
...
also other clarifications and corrections.
2019-01-08 00:25:06 +00:00
e789eb186a
link to MSC1711
2018-11-12 14:02:53 +00:00
b1e79ac7ab
Update 1708-well-known-for-federation.md
2018-11-09 11:22:22 +00:00
09d41464e7
Add problems section
...
xs
2018-11-06 11:39:08 +00:00
c4e1949cf8
Clarifications about what `server` means
2018-11-06 11:39:08 +00:00
e3f10a4fd2
Update 1708-well-known-for-federation.md
...
fix title
2018-11-05 18:37:25 +00:00
87330b9b9b
Proposal for .well-known for server discovery
2018-11-05 18:23:23 +00:00
Travis Ralston