Difference between revisions of "XEP ideas/Server status page"
Jump to navigation
Jump to search
m (→DNS: URI records have priority and weight like SRV records) |
|||
| Line 9: | Line 9: | ||
=== DNS === | === DNS === | ||
''_status.jabberfr.org IN URI "https://statut.jabberfr.org/"'' | ''_status.jabberfr.org IN URI 0 0 "https://statut.jabberfr.org/"'' | ||
([https://tools.ietf.org/html/rfc7553 URI resource record]) | ([https://tools.ietf.org/html/rfc7553 URI resource record]) | ||
Revision as of 11:23, 23 April 2020
A way for clients to obtain the status page of a service that it could display to users when said service is experiencing issues.
https://mail.jabber.org/pipermail/standards/2018-December/035514.html
0157 Contact Addresses for XMPP Services
Clients would have to cache it to display it back when it's necessary
DNS
_status.jabberfr.org IN URI 0 0 "https://statut.jabberfr.org/"
DNS having more chance to be alive when the server is down, this would prevent the need for caching. It might require services allowing users to have their own domain to also indicate that they need to setup another record for their users.
<stream:error/> answer
Maybe all is needed is an entity replying something along the lines of <stream:error><system-shutdown/><text>Service down because reasons.<////>