```
$ gpac -logs=network@debug -i https://livesim2.dashif.org/livesim2/testpic_2s/Manifest.mpd dashin:forward=file -o mabr://225.1.1.0:6000:gpac:NCID=ID1
 -netcap=dst=id=ID1,flute.gpc
[Sock_IPV6] Solving livesim2.dashif.org address
[Sock_IPV6] Host livesim2.dashif.org found
[TLSv1.0] TLS header Certificate Status (22)
[TLSv1.3] TLS handshake Client hello (1)
���Y�ୱ�o.\�__�ݜ�jb��[q� �q��B�E��9G#�k�v�<z�1��h��nķ>�,�0�̨̩̪�+�/��$�(k�#�'g�
�9�     �3��=<5/�ulivesim2.dashif.org

*(

+-3&$ G�g��တ-aչQ��_�������u�Gz�^C
```

Switching the source to HTTP removes the garbage.

PS: can't make netcap work with FLUTE
netcap with https displays garbage
This is a GitHub Issue
repo:gpac
owner:gpac
Title : netcap with https displays garbage
Issue date:

--- start body ---
```
$ gpac -logs=network@debug -i https://livesim2.dashif.org/livesim2/testpic_2s/Manifest.mpd dashin:forward=file -o mabr://225.1.1.0:6000:gpac:NCID=ID1
 -netcap=dst=id=ID1,flute.gpc
[Sock_IPV6] Solving livesim2.dashif.org address
[Sock_IPV6] Host livesim2.dashif.org found
[TLSv1.0] TLS header Certificate Status (22)
[TLSv1.3] TLS handshake Client hello (1)
���Y�ୱ�o.\�__�ݜ�jb��[q� �q��B�E��9G#�k�v�<z�1��h��nķ>�,�0�̨̩̪�+�/��$�(k�#�'g�
�9�     �3��=<5/�ulivesim2.dashif.org

*(

+-3&$ G�g��တ-aչQ��_�������u�Gz�^C
```

Switching the source to HTTP removes the garbage.

PS: can't make netcap work with FLUTE
--- end body ---

The issue describes a problem with the netcap feature in GPAC when using HTTPS, resulting in corrupted output (garbage) during the network capture process. This could indicate a potential vulnerability related to improper handling of encrypted data or a bug in the implementation of the netcap feature with HTTPS. However, it is more likely a bug rather than a security vulnerability, as it does not appear to expose sensitive data or allow for exploitation.