Menu

#12 Support custom nginx status codes

Future Release
closed
nobody
nginx (1)
5
2019-04-17
2019-04-15
No

Would be nice to habe the two custom nginx status codes supported:

444 -> Connection closed without response
499 -> Client closed request

Currently I patched the /usr/share/logwatch/scripts/services/http file for this.

Discussion

  • Bjorn

    Bjorn - 2019-04-15

    The codes you list are not assigned by IANA. So when you say custom, I assume these are codes you assigned in your http server. I'd encourage to use standard IANA-assigned codes. I just updated the list in the http script (in the git repository) with the current assignments.

    If you do prefer to have a custom http script, the preferred location is /etc/logwatch/scripts/services/http, rather than under /usr/share, as that way it does not get overwritten at every update.

     
  • Bjorn

    Bjorn - 2019-04-16
    • status: open --> closed
     
  • Bjorn

    Bjorn - 2019-04-16

    I see; they are defined as custom by nginx. I've added the six custom codes to the http filter, as they do not appear to conflict with any other major http server software. Should IANA (official registry of HTTP status codes) define these codes , we'll have to update the file.

     
  • Fabian Dellwing

    Fabian Dellwing - 2019-04-17

    Thanks a lot :)

     

Log in to post a comment.

MongoDB Logo MongoDB