Replace the use of Exceptions in middlewares
authorTim Düsterhus <duesterhus@woltlab.com>
Thu, 13 Apr 2023 09:29:09 +0000 (11:29 +0200)
committerTim Düsterhus <duesterhus@woltlab.com>
Thu, 13 Apr 2023 12:20:16 +0000 (14:20 +0200)
commitb8977a0f567a7b679f04c4b594785b1868796eb5
tree113a64c3a110ce434e47a11429167dd579e2d3d8
parent3caf16633c42b31344659aba38883c106c851a50
Replace the use of Exceptions in middlewares

This is problematic, because Exceptions will skip the response direction of the
middleware stack. Instead appropriate responses are either generated directly
or forwarded to an appropriate request handler.
wcfsetup/install/files/lib/http/error/OfflineHandler.class.php [new file with mode: 0644]
wcfsetup/install/files/lib/http/middleware/CheckForEnterpriseNonOwnerAccess.class.php
wcfsetup/install/files/lib/http/middleware/CheckForExpiredAppEvaluation.class.php
wcfsetup/install/files/lib/http/middleware/CheckForOfflineMode.class.php
wcfsetup/install/files/lib/http/middleware/CheckSystemEnvironment.class.php
wcfsetup/install/files/lib/http/middleware/CheckUserBan.class.php
wcfsetup/install/files/lib/http/middleware/EnforceAcpAuthentication.class.php
wcfsetup/install/files/lib/http/middleware/HandleValinorMappingErrors.class.php