Curl reports excess content found. Normal?

[ddevienne]

The default built-in response when not finding a route lacks a Content-Length header,
yet seems to have content, which CURL reports as excess. Might need fixing? Just FYI.

I probably need to have a catch all wildcard route, and report my own error I guess.

C:\Users\ddevienne>curl -v -I "http://localhost:8899/api/v1/acme"
*   Trying 127.0.0.1:8899...
* Connected to localhost (127.0.0.1) port 8899 (#0)
> HEAD /api/v1/acme HTTP/1.1
> Host: localhost:8899
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 404 File Not Found
HTTP/1.1 404 File Not Found

<
* Excess found: excess = 55 url = /api/v1/acme (zero-length body)
* Connection #0 to host localhost left intact

[uNetworkingAB]

c5aab19

this should fix it

[ddevienne]

Seems a bit severe to close the connection, although I kinda see your point, and you know best. Thanks.

[uNetworkingAB]

ideally 404 should not close connection but all other errors should. 404 needs to move somewhere else