From 8b763b9fdf5cddc3ebe3027f2d5acb17f6402eed Mon Sep 17 00:00:00 2001 From: Gabriel Augendre Date: Tue, 17 Oct 2023 18:42:36 +0200 Subject: [PATCH] fix pre-commit --- content/posts/gin-method-not-allowed/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/gin-method-not-allowed/index.md b/content/posts/gin-method-not-allowed/index.md index b0ee2d3..a281d8c 100644 --- a/content/posts/gin-method-not-allowed/index.md +++ b/content/posts/gin-method-not-allowed/index.md @@ -24,7 +24,7 @@ TL;DR: by default `gin` returns a 404 for an incorrect HTTP verb sent to a handl ## 📖 Context At OVHcloud, we use [`gin-gonic/gin`](https://github.com/gin-gonic/gin) as the go-to HTTP web framework for our internal services. -The default behavior when receiving a request for a path that's handled but with an incorrect HTTP verb is to reply with `404 Not Found`. +The default behavior when receiving a request for a path that's handled but with an incorrect HTTP verb is to reply with `404 Not Found`. That's confusing because this status code is more often used when a path is not handled at all. {{< highlight go "linenos=inline" >}}