Use clearer error pages' titles

This commit is contained in:
Dan 2018-12-29 13:37:13 +01:00
parent 554512d43b
commit d00fde74de
9 changed files with 23 additions and 23 deletions

View File

@ -1,5 +1,5 @@
Bad Request 400 - Bad Request
=========== =================
.. module:: pyrogram.api.errors.BadRequest .. module:: pyrogram.api.errors.BadRequest

View File

@ -1,5 +1,5 @@
Flood 420 - Flood
===== ===========
.. module:: pyrogram.api.errors.Flood .. module:: pyrogram.api.errors.Flood

View File

@ -1,5 +1,5 @@
Forbidden 403 - Forbidden
========= ===============
.. module:: pyrogram.api.errors.Forbidden .. module:: pyrogram.api.errors.Forbidden

View File

@ -1,5 +1,5 @@
Internal Server Error 500 - Internal Server Error
===================== ===========================
.. module:: pyrogram.api.errors.InternalServerError .. module:: pyrogram.api.errors.InternalServerError

View File

@ -1,5 +1,5 @@
Not Acceptable 406 - Not Acceptable
============== ====================
.. module:: pyrogram.api.errors.NotAcceptable .. module:: pyrogram.api.errors.NotAcceptable

View File

@ -1,5 +1,5 @@
See Other 303 - See Other
========= ===============
.. module:: pyrogram.api.errors.SeeOther .. module:: pyrogram.api.errors.SeeOther

View File

@ -1,5 +1,5 @@
Unauthorized 401 - Unauthorized
============ ==================
.. module:: pyrogram.api.errors.Unauthorized .. module:: pyrogram.api.errors.Unauthorized

View File

@ -1,5 +1,5 @@
Unknown Error 520 - Unknown Error
============= ===================
.. module:: pyrogram.api.errors.UnknownError .. module:: pyrogram.api.errors.UnknownError

View File

@ -6,13 +6,13 @@ Errors are inevitable when working with the API, and they must be correctly hand
There are many errors that Telegram could return, but they all fall in one of these categories There are many errors that Telegram could return, but they all fall in one of these categories
(which are in turn children of the :obj:`pyrogram.Error` superclass) (which are in turn children of the :obj:`pyrogram.Error` superclass)
- :obj:`303 See Other <pyrogram.api.errors.SeeOther>` - :obj:`303 - See Other <pyrogram.api.errors.SeeOther>`
- :obj:`400 Bad Request <pyrogram.api.errors.BadRequest>` - :obj:`400 - Bad Request <pyrogram.api.errors.BadRequest>`
- :obj:`401 Unauthorized <pyrogram.api.errors.Unauthorized>` - :obj:`401 - Unauthorized <pyrogram.api.errors.Unauthorized>`
- :obj:`403 Forbidden <pyrogram.api.errors.Forbidden>` - :obj:`403 - Forbidden <pyrogram.api.errors.Forbidden>`
- :obj:`406 Not Acceptable <pyrogram.api.errors.NotAcceptable>` - :obj:`406 - Not Acceptable <pyrogram.api.errors.NotAcceptable>`
- :obj:`420 Flood <pyrogram.api.errors.Flood>` - :obj:`420 - Flood <pyrogram.api.errors.Flood>`
- :obj:`500 Internal Server Error <pyrogram.api.errors.InternalServerError>` - :obj:`500 - Internal Server Error <pyrogram.api.errors.InternalServerError>`
As stated above, there are really many (too many) errors, and in case Pyrogram does not know anything yet about a As stated above, there are really many (too many) errors, and in case Pyrogram does not know anything yet about a
specific one, it raises a special :obj:`520 Unknown Error <pyrogram.api.errors.UnknownError>` exception and logs it specific one, it raises a special :obj:`520 Unknown Error <pyrogram.api.errors.UnknownError>` exception and logs it