New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server should return unavailableCriticalExtension when processing a badly formed critical control #600
Comments
Comment from tbordaz (@tbordaz) at 2013-03-13 20:11:52 attachment |
Comment from tbordaz (@tbordaz) at 2013-03-13 20:19:27 attachment |
Comment from tbordaz (@tbordaz) at 2013-03-22 15:06:51 '''Git merge+push''' (note I used new_branch_name to work on ticket600) git merge new_branch_name git push origin master |
Comment from tbordaz (@tbordaz) at 2013-03-22 15:46:53 commit e84c63f |
Comment from nkinder (@nkinder) at 2013-04-02 03:18:23 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=947243 |
Comment from tbordaz (@tbordaz) at 2014-02-05 19:27:55 attachment |
Comment from tbordaz (@tbordaz) at 2014-02-05 19:28:08 attachment |
Comment from tbordaz (@tbordaz) at 2017-02-11 22:58:06 Metadata Update from @tbordaz:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/600
According to http://www.ietf.org/rfc/rfc4511.txt, the server should return unavailableCriticalExtension when receiving a badly formed critical control (null length or/and null value). Currently the return value is always protocol error whatever the critical flag is true/fals
The text was updated successfully, but these errors were encountered: