forked from boostorg/beast
* teardown_tag is replaced with teardown_role, a client/server flag used to determine whether the shutdown is performed before or after reading the EOF. This is in accordance with RFC6455 7.1.1: https://tools.ietf.org/html/rfc6455#section-7.1.1 Actions Required: * Modify signatures of teardown and async_teardown to use teardown_role instead of teardown_tag * Change calls to teardown and async_teardown to pass the correct role: client or server depending on context.
62 lines
1.3 KiB
C++
62 lines
1.3 KiB
C++
//
|
|
// Copyright (c) 2016-2017 Vinnie Falco (vinnie dot falco at gmail dot com)
|
|
//
|
|
// Distributed under the Boost Software License, Version 1.0. (See accompanying
|
|
// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
|
|
//
|
|
// Official repository: https://github.com/boostorg/beast
|
|
//
|
|
|
|
#ifndef BOOST_BEAST_WEBSOCKET_IMPL_SSL_IPP_INCLUDED
|
|
#define BOOST_BEAST_WEBSOCKET_IMPL_SSL_IPP_INCLUDED
|
|
|
|
#include <utility>
|
|
|
|
namespace boost {
|
|
namespace beast {
|
|
namespace websocket {
|
|
|
|
/*
|
|
|
|
See
|
|
http://stackoverflow.com/questions/32046034/what-is-the-proper-way-to-securely-disconnect-an-asio-ssl-socket/32054476#32054476
|
|
|
|
Behavior of ssl::stream regarding close_
|
|
|
|
If the remote host calls async_shutdown then the
|
|
local host's async_read will complete with eof.
|
|
|
|
If both hosts call async_shutdown then the calls
|
|
to async_shutdown will complete with eof.
|
|
|
|
*/
|
|
|
|
template<class AsyncStream>
|
|
void
|
|
teardown(
|
|
role_type,
|
|
boost::asio::ssl::stream<AsyncStream>& stream,
|
|
error_code& ec)
|
|
{
|
|
stream.shutdown(ec);
|
|
}
|
|
|
|
template<
|
|
class AsyncStream,
|
|
class TeardownHandler>
|
|
void
|
|
async_teardown(
|
|
role_type,
|
|
boost::asio::ssl::stream<AsyncStream>& stream,
|
|
TeardownHandler&& handler)
|
|
{
|
|
stream.async_shutdown(
|
|
std::forward<TeardownHandler>(handler));
|
|
}
|
|
|
|
} // websocket
|
|
} // beast
|
|
} // boost
|
|
|
|
#endif
|