You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2015-11-27.00:30:04.411>labels= ['type-feature', 'library']
title='Add PAYLOAD_TOO_LARGE / URI_TOO_LONG (new name in RFC 7231)'updated_at=<Date2020-09-18.05:51:47.742>user='https://github.com/spaceone'
spaceonemannequin
changed the title
Add PAYLOAD_TOO_LARGE (new name in RFC 7231)
Add PAYLOAD_TOO_LARGE / URI_TOO_LONG (new name in RFC 7231)
Nov 27, 2015
In general, I’m not sure it is worth adding aliases for various names used in different RFCs. But you could argue that this is appropriate because the old names are unnecessarily long. Another example would be HTTPStatus.REQUESTED_RANGE_NOT_SATISFIABLE vs “Range Not Satisfiable” <https://tools.ietf.org/html/rfc7233#section-4.4\>.
If we were to go ahead with this, it would need a documentation update. A test case would also be nice, ensuring that the new name is the “one true” name, and the old name is an alias.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: