chore: when decoding a response, the decoder now attempts to automati…

…cally determine the encoding via the `Content-Type` header

CHANGELOG.md

@@ -6,6 +6,10 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
 
 ## [2.2.2] - 2023-10-29
 
+### Changed
+
+- When decoding a response, the decoder now attempts to automatically determine the encoding via the `Content-Type` header.
+
 ### Fixed
 
 - Fixed an issue where the application would get confused about the session state if the user logs out globally via the forum's logout functionality.

src/http/http.service.ts

@@ -46,7 +46,11 @@ export class HttpService {
         ),
     );
     if (decode) {
-      const decoder = new TextDecoder('iso-8859-15');
+      const contentTypeHeader: string = (response as any).headers[
+        'content-type'
+      ];
+      const decoding = contentTypeHeader?.split('charset=')[1];
+      const decoder = new TextDecoder(decoding?.toLowerCase() ?? 'iso-8859-15');
       const text = decoder.decode(response.data as ArrayBuffer);
       response.data = text;
     }

src/threads/controllers/threads.controller.ts

@@ -87,7 +87,6 @@ export class ThreadsController {
     @Request() request: ExpressRequest,
     @Query() query: ThreadsFindByIdQuery,
   ): Promise<ThreadReadResource> {
-    console.log(query);
     return this.service.findById(id, request.user, {
       ...query,
     });