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
{{ message }}
This repository was archived by the owner on May 16, 2018. It is now read-only.
Session Validators (like Zend_Session_Validator_HttpUserAgent), provide an easy and extendable mechanism to validate sessions during startup.
However, when validation fails during session startup, a general Zend_Session_Exception is thrown. The same Zend_Session_Exception can be thrown due to other causes, for example:
How can one be sure that an Exception caught during session start was caused by a certain Validator that fails? Would it not be better to have:
either a general Exception class used by all Validators: Zend_Session_Validator_Exception, this would be better than nothing, but when using multiple Exceptions this also might become to 'general'
or a per-validator specific Exception, for example: Zend_Session_Validator_HttpUserAgent_Exception
Maybe I am missing something, but in case one of the aforementioned solutions is regarded viable, I can come up with a PR, starting with the first suggestion which seems quite straight forward.
The text was updated successfully, but these errors were encountered:
Session Validators (like Zend_Session_Validator_HttpUserAgent), provide an easy and extendable mechanism to validate sessions during startup.
However, when validation fails during session startup, a general Zend_Session_Exception is thrown. The same Zend_Session_Exception can be thrown due to other causes, for example:
How can one be sure that an Exception caught during session start was caused by a certain Validator that fails? Would it not be better to have:
Maybe I am missing something, but in case one of the aforementioned solutions is regarded viable, I can come up with a PR, starting with the first suggestion which seems quite straight forward.
The text was updated successfully, but these errors were encountered: