[
https://issues.apache.org/jira/browse/PROTOCOLS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved PROTOCOLS-30.
------------------------------------
Resolution: Fixed
done
> STARTTLS handling is not correct and can cause touble execution of the
> STARTTLS handling
> ----------------------------------------------------------------------------------------
>
> Key: PROTOCOLS-30
> URL: https://issues.apache.org/jira/browse/PROTOCOLS-30
> Project: JAMES Protocols
> Issue Type: Bug
> Components: api, smtp
> Affects Versions: 1.5
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 1.6
>
>
> When we handler STARTTLS we are current write the Response to the client via
> Session.write(...) , then trigger Session.startTLS() and then return null
> from the CommandHandler. The problem is that returning null tells the
> LineHandler to execute the next CommandHandler as it things we was not able
> to handle the Request. It would be better to return a special type of
> Response and let the linehandler/Session handle all the other parts
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
