On 14/06/15 17:12, wm4 wrote:
> GNUTLS_SHUT_RDWR means GnuTLS will keep waiting for the server's
> termination reply. But since we don't shutdown the TCP connection at
> this point yet, GnuTLS will just keep skipping actual data from the
> server, which basically is perceived as hang.
> 
> Use GNUTLS_SHUT_WR instead, which doesn't have this problem.
> ---
>  libavformat/tls_gnutls.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libavformat/tls_gnutls.c b/libavformat/tls_gnutls.c
> index 0fade36..a5d7e89 100644
> --- a/libavformat/tls_gnutls.c
> +++ b/libavformat/tls_gnutls.c
> @@ -87,7 +87,7 @@ static int tls_close(URLContext *h)
>  {
>      TLSContext *c = h->priv_data;
>      if (c->need_shutdown)
> -        gnutls_bye(c->session, GNUTLS_SHUT_RDWR);
> +        gnutls_bye(c->session, GNUTLS_SHUT_WR);
>      if (c->session)
>          gnutls_deinit(c->session);
>      if (c->cred)
> 

Seems fine to me. Thanks a lot!
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to