Merge pull request #3 from dniccum/bugfix/response-body-overload-prot…

…ection

Bugfix/response body overload protection

README.md

@@ -117,6 +117,10 @@ Route::post('/create-project', [ \App\Http\Controllers\SampleController::class,
     ->middleware([ 'route-logging' ]);
 ```
 
+#### IMPORTANT: Response Body Length Limit
+
+Assuming that your database migration and model are unchanged, there is currently logic in place that will prevent the `response_body` column from being overloaded. What does this mean? In the event that the response body of the request that you are logging is very large (ie returning 500+ results from an API), the number of bytes/characters might be too large for the database to store without failing. If the response body **is longer than 65,000 characters, the response body will NOT be saved.**
+
 ### Log Cleanup (optional)
 
 **Note** – this is not required but *HIGHLY* recommended as this could lead to large amounts of data within your database in short periods of time.

src/Http/Middleware/RequestLogging.php

@@ -61,7 +61,11 @@ public function terminate(Request $request, JsonResponse $response)
         $logEntry->request_header = $request->header();
         $logEntry->ip = $request->ip();
         $logEntry->status_code = $response->getStatusCode();
-        $logEntry->response_body = json_decode($response->getContent(), true);
+        if ($response->getContent() && strlen($response->getContent()) <= 65000) {
+            $logEntry->response_body = json_decode($response->getContent(), true);
+        } else {
+            $logEntry->response_body = 'Response was too long to store.';
+        }
         $logEntry->save();
     }