[
https://issues.apache.org/jira/browse/TINKERPOP-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420702#comment-17420702
]
ASF GitHub Bot commented on TINKERPOP-2616:
-------------------------------------------
spmallette commented on pull request #1479:
URL: https://github.com/apache/tinkerpop/pull/1479#issuecomment-927817165
> I would vote that we can take this break in exception contract for 3.5.x
series since that is still going through some stabilization with respect to
other behaviours as well such as null semantics.
For this particular modification, I'd be ok with taking this minor breaking
change in 3.5-dev as long as there is an upgrade doc entry to support it.
Backporting the change to 3.4-dev without the breaking change also makes
sense to me. Assuming all that is in place:
VOTE +1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Provide better exceptions with SSL related failures
> ---------------------------------------------------
>
> Key: TINKERPOP-2616
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2616
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.4.12
> Reporter: Stephen Mallette
> Priority: Minor
>
> Propagate SSL exception to the client. Currently, if an error occurs during
> connection setup, client observes a generic “connection failed error”. This
> is because server has no mechanism to send an exact error to the client since
> the connection was never setup. The idea is to use WebSocket error codes to
> provide a more specific error to the client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
