Is HTTP 200 correct here?

[MegaManSec]

$ curl -sk -i -H 'accept: application/dns-message'   "https://127.0.0.1:3000/dns-query?dns=$(perl -e 'print "!" x 20')"
HTTP/2 400 
content-type: text/plain
server: dnscrypt-proxy
content-length: 32
date: Wed, 24 Sep 2025 17:34:25 GMT

dnscrypt-proxy local DoH server


$ curl -sk -i -H 'accept: application/dns-message'   "https://127.0.0.1:3000/dns-query?dns=$(perl -e 'print "!" x 200')"
HTTP/2 200 
server: dnscrypt-proxy
content-length: 0
date: Wed, 24 Sep 2025 17:20:01 GMT

rfc says:

   The 2xx (Successful) class of status code indicates that the client's
   request was successfully received, understood, and accepted.
[..]
   The 200 (OK) status code indicates that the request has succeeded.
   The payload sent in a 200 response depends on the request method.
   For the methods defined by this specification, the intended meaning
   of the payload can be summarized as:
[..]
   Aside from responses to CONNECT, a 200 response always has a payload,
   though an origin server MAY generate a payload body of zero length.
   If no payload is desired, an origin server ought to send 204 (No
   Content) instead.  For CONNECT, no payload is allowed because the
   successful result is a tunnel, which begins immediately after the 200
   response header section.

i am not sure that 20 ! characters should differ from 200 at all, and i do not think it falls into the "may generate a payload body of zero length" category

[jedisct1]

Thanks!

40def34 should address that.

[MegaManSec]

should the other paths be updated? e.g. e.g. L61, 48, 40, 23