Fix TCP proxy to pass through responses without Content-Type header

When no Content-Type header is present, default to binary pass-through
instead of attempting URL rewriting. DLNA text responses (XML) always
include Content-Type headers, while media streams (like DVB) may omit them.

Fixes #4

Author: fenio

CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
 
 This project is a fork of [Nic0w/dlnaproxy](https://github.com/Nic0w/dlnaproxy).
 
+## [0.4.5] - 2026-01-09
+
+### Fixed
+
+- **TCP proxy: default to binary pass-through when Content-Type is missing**: Responses without a Content-Type header are now passed through unchanged instead of attempting URL rewriting. This fixes streaming from DVB and other servers that don't send Content-Type headers for media streams.
+
 ## [0.4.4] - 2026-01-09
 
 ### Fixed

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "dlna-proxy"
-version = "0.4.4"
+version = "0.4.5"
 authors = ["Nic0w", "Bartosz Fenski <fenio@debian.org>"]
 edition = "2021"
 description = "A DLNA proxy that enables use of a DLNA server past the local network boundary"

src/tcp_proxy.rs

@@ -191,8 +191,10 @@ fn should_rewrite_content(headers: &str) -> bool {
                 || content_type.contains("html");
         }
     }
-    // If no Content-Type header, assume it might be text (for compatibility)
-    true
+    // If no Content-Type header, default to binary pass-through.
+    // DLNA text responses (XML) always have Content-Type headers,
+    // while media streams may omit them.
+    false
 }
 
 /// Proxy HTTP responses from origin to client, rewriting URLs in the body