Mercurial > p > roundup > code
view roundup/exceptions.py @ 7068:bc06bad26872
Remove dead code for handling LogoutAction.
Dead code starts wih:
'''
# I think now that LogoutAction redirects to
# self.base ([tracker] web parameter in config.ini),
# this code is not needed. However I am keeping it
# around in case it has to come back to life.
# Delete if this is still around in 3/2018.
# rouilj 3/2017.
#
# Note using this code may cause a CSRF Login vulnerability.
# Handle the case where user logs out and tries to
# log in again in same window.
# The csrf token for the login button is associated
# with the prior login, so it will not validate.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 23 Nov 2022 22:25:34 -0500 |
| parents | c177e7128dc9 |
| children | e16b7d47fdb2 |
line wrap: on
line source
"""Exceptions for use across all Roundup components. """ __docformat__ = 'restructuredtext' class RoundupException(Exception): pass class LoginError(RoundupException): pass class Unauthorised(RoundupException): pass class RejectBase(RoundupException): pass class Reject(RejectBase): """An auditor may raise this exception when the current create or set operation should be stopped. It is up to the specific interface invoking the create or set to handle this exception sanely. For example: - mailgw will trap and ignore Reject for file attachments and messages - cgi will trap and present the exception in a nice format """ pass class RejectRaw(Reject): """ Performs the same function as Reject, except HTML in the message is not escaped when displayed to the user. """ pass class UsageError(ValueError): pass # vim: set filetype=python ts=4 sw=4 et si
