Internal data flow error using soup gstreamer plugin

HelloIn a gstreamer context I would appreciate to have matroskademux working with soup gstreamer plugin.In 90% of case this is working fine but with some files (I put one in attachement) this is not the case.The way I launch it for debugging on a Ubuntu station is very simple:./GST_DEBUG=3 gst-launch souphttpsrc location="http://@myHTTPServeur/CONT-4G.mkv" ! matroskademux ! fakesinkIn the trace I systematically got following error:
0:00:01.148526470  3096  0x8103680 ERROR               ebmlread ebml-read.c:155:gst_ebml_peek_id_length:<matroskademux0> Invalid EBML length size tag (0x0) at position 2373 (0x945)0:00:01.148896314  3096  0x8103680 INFO        GST_ERROR_SYSTEM gstelement.c:1931:gst_element_message_full:<souphttpsrc0> posting message: Internal data flow error.0:00:01.149049227  3096  0x8103680 INFO        GST_ERROR_SYSTEM gstelement.c:1954:gst_element_message_full:<souphttpsrc0> posted error message: Internal data flow error.0:00:01.149179521  3096  0x8103680 WARN           matroskademux matroska-demux.c:4644:gst_matroska_demux_handle_sink_event:<matroskademux0> error: got eos and didn't receive a complete header object
In fact by using mkvtoolnix I notice that with this specific file the "Segment Infos" are before the "Seek infos" which is not the case in other working files and which is not the case in the matroska spec, isnt' it?Other thing to know is that soup plugin is working in a push mode contrary to pull mode (like filesrc working fine for example) .
Is it a limitation of matroska demux working with push gstreamer source plugin or is it this file that is not correct (my fear is then how many files like this can exist on net) or is  there something in my command line I forgot to pass to make it working correctly?I hope I was clear with my explanations.Have a good day and thanks for your future answer.Nicolas izzet.