add all
This commit is contained in:
32
Packages/com.tivadar.best.http/Runtime/3rdParty/BouncyCastle/tls/TlsNoCloseNotifyException.cs
vendored
Normal file
32
Packages/com.tivadar.best.http/Runtime/3rdParty/BouncyCastle/tls/TlsNoCloseNotifyException.cs
vendored
Normal file
@@ -0,0 +1,32 @@
|
||||
#if !BESTHTTP_DISABLE_ALTERNATE_SSL && (!UNITY_WEBGL || UNITY_EDITOR)
|
||||
#pragma warning disable
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Runtime.Serialization;
|
||||
|
||||
namespace Best.HTTP.SecureProtocol.Org.BouncyCastle.Tls
|
||||
{
|
||||
/// <summary>This exception will be thrown (only) when the connection is closed by the peer without sending a
|
||||
/// <see cref="AlertDescription.close_notify">close_notify</see> warning alert.</summary>
|
||||
/// <remarks>
|
||||
/// If this happens, the TLS protocol cannot rule out truncation of the connection data (potentially
|
||||
/// malicious). It may be possible to check for truncation via some property of a higher level protocol
|
||||
/// built upon TLS, e.g.the Content-Length header for HTTPS.
|
||||
/// </remarks>
|
||||
[Serializable]
|
||||
public class TlsNoCloseNotifyException
|
||||
: EndOfStreamException
|
||||
{
|
||||
public TlsNoCloseNotifyException()
|
||||
: base("No close_notify alert received before connection closed")
|
||||
{
|
||||
}
|
||||
|
||||
protected TlsNoCloseNotifyException(SerializationInfo info, StreamingContext context)
|
||||
: base(info, context)
|
||||
{
|
||||
}
|
||||
}
|
||||
}
|
||||
#pragma warning restore
|
||||
#endif
|
||||
Reference in New Issue
Block a user