Mixdrop extractor fails with "Request URL is missing an 'http://' or 'https://' protocol."

[webstreamr]

it generically started failing with "Request URL is missing an 'http://' or 'https://' protocol." which is worrying me a bit more :/

Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: REDACTED:0 - "GET /extractor/video?host=Mixdrop&api_password=REDACTED&d=https%3A%2F%2Fmixdrop.ag%2Fe%2Fwn4kmeg8b0g0e8j&redirect_stream=true HTTP/1.0" 302
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: REDACTED:0 - "HEAD /extractor/video?host=Mixdrop&api_password=REDACTED&d=https%3A%2F%2Fmixdrop.ag%2Fe%2Fwn4kmeg8b0g0e8j&redirect_stream=true HTTP/1.0" 302
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: 2025-07-16 10:03:03,230 - mediaflow_proxy.utils.http_utils - ERROR - Error creating streaming response: Request URL is missing an 'http://' or 'https://' protocol.
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: REDACTED:0 - "GET /extractor/video?host=Mixdrop&api_password=REDACTED&d=https%3A%2F%2Fmixdrop.ag%2Fe%2Fwn4kmeg8b0g0e8j&redirect_stream=true HTTP/1.0" 302
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: 2025-07-16 10:03:03,319 - mediaflow_proxy.utils.http_utils - ERROR - Error creating streaming response: Request URL is missing an 'http://' or 'https://' protocol.
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: 2025-07-16 10:03:03,482 - mediaflow_proxy.utils.http_utils - ERROR - Error creating streaming response: Request URL is missing an 'http://' or 'https://' protocol.
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: 2025-07-16 10:03:03,508 - mediaflow_proxy.utils.http_utils - ERROR - Error creating streaming response: Request URL is missing an 'http://' or 'https://' protocol.
Jul 16 10:03:03 instance-20250423-1100 docker[1442922]: REDACTED:0 - "GET /proxy/stream?api_password=REDACTED&d=https%3A%22%2F%2Fa-delivery23.mxcontent.net%2F1mxcontent%2Fwn4kmeg8b0g0e8j.mp4%3F1mp4%3DdAWDR9x8jHK8wpQyMGmecA%261wn4kmeg8b0g0e8j%3D1referrer%261net%3D1dAWDR9x8jHK8wpQyMGmecA&h_user-agent=Mozilla%2F5.0+%28Windows+NT+10.0%3B+Win64%3B+x64%29+AppleWebKit%2F537.36+%28KHTML%2C+like+Gecko%29+Chrome%2F136.0.0.0+Safari%2F537.36&h_range=bytes%3D0-&h_accept-language=en-US%2Cen%3Bq%3D0.5&h_referer=https%3A%2F%2Fmixdrop.ag%2Fe%2Fwn4kmeg8b0g0e8j HTTP/1.0" 502

I hope I can look into it, if not @UrloMythus is faster again 😅

[webstreamr]

ah I see, a quick check with e.g. https://mixdrop.my/e/wn4kmeg8b0g0e8j shows that Mixdrop seems to be also using p.a.c.k.e.d. JS. maybe it makes sense to merge #118 first before digging into the Mixdrop unpacking logic? fyi @mhdzumair 🙇‍♂️

but based on the last request in the logs above it looks like it could get some mxcontent URL at some point. so not fully sure yet what the issue is. but using the unpacker feels safer any way I guess.

UPDATE: can confirm something's wrong with the unpacker creating the final_url. they start like e.g. https:"//a-delivery23.mxcontent.net, but that's not all