Merge pull request #7 from GhostTypes/bolt/optimize-proxy-response-852645102297276780

⚡ Bolt: Use response.content to avoid decoding overhead in proxy

Author: GhostTypes

.jules/bolt.md

@@ -0,0 +1,3 @@
+## 2024-05-23 - Decoding Overhead in Proxy Servers
+**Learning:** Accessing `response.text` in Python's `requests` library triggers automatic encoding detection and decoding, which is computationally expensive (measured 260x slower than `.content` for large payloads). For proxy servers, this is often unnecessary waste as the data just needs to be forwarded.
+**Action:** When building proxies or pass-through services, always prefer raw bytes (`.content`) and forward the original `Content-Type` header to avoid double-transcoding (upstream -> unicode -> utf-8).

server.py

@@ -108,10 +108,9 @@ def clean_headers(response):
 def generate_proxy_response(response) -> Response:
     content_type = response.headers.get('content-type', '')
 
-    if 'text' in content_type or 'html' in content_type:
-        content = response.text
-    else:
-        content = response.content
+    # OPTIMIZATION: Use .content (bytes) to avoid decoding overhead
+    # This provides significant performance improvement and avoids potential transcoding issues.
+    content = response.content
 
     headers = clean_headers(response)
 
@@ -121,7 +120,8 @@ def generate_proxy_response(response) -> Response:
 
     # For HTML content
     if 'text/html' in content_type:
-        return Response(content, status=response.status_code, content_type='text/html; charset=utf-8')
+        # Use the original content type to ensure charset matches the raw bytes
+        return Response(content, status=response.status_code, content_type=content_type)
 
     # For all other content types
     return Response(