recorder: set content_type for Response in Recorder._on_request

Recorder._on_request does not set the content_type parameter when
creating a new Response instance. When content_type is not set the
Response.__init__ will always set the value to "text/plain". This means
the recording file is always written with that content type and when
responses are replayed they may not have their original content-type
header value.

For example, the python-gitlab package expects the response header
content type to be 'application/json' but this information is in the
recording and playing it back will fail.

Fix this by having _on_request() pass in the content_type of the
requests_response.header.

Signed-off-by: Patrick Talbert <[email protected]>

Author: ptalbert

responses/_recorder.py

@@ -144,13 +144,20 @@ def _on_request(
         headers_values = {
             key: value for key, value in requests_response.headers.items()
         }
-        responses_response = Response(
-            method=str(request.method),
-            url=str(requests_response.request.url),
-            status=requests_response.status_code,
-            body=requests_response.text,
-            headers=headers_values,
-        )
+
+        response_params = {
+            "method": str(request.method),
+            "url": str(requests_response.request.url),
+            "status": requests_response.status_code,
+            "body": requests_response.text,
+            "headers": headers_values,
+        }
+
+        # If the header has a content type then pass it in.
+        if content_type := requests_response.headers.get("content-type"):
+            response_params["content_type"] = content_type
+
+        responses_response = Response(**response_params)
         self._registry.add(responses_response)
         return requests_response