mod_http: Limit unencrypted http port (5280) to loopback by default Since accessing this port directly over the wider Internet is unlikely to intentional anymore. Most uses will likely be by reverse proxies, by mistake or because of trouble configuring HTTPS. Blocking mistaken uses is just a good thing, letting users send potentially private things unencrypted tends to be Strongly Discouraged these days. Many reverse proxy setups operate over loopback, so listening there instead of all interfaces is a net improvement. Improved automatic certificate location and SNI support has mostly eliminated the need for manual certificate configuration so HTTPS should Just Work once certificates have been provided. For local testing during development, connecting over loopback is likely fine as well. When really needed, `http_interfaces` can still be set. Suggested by Link Mauve

     1

rules:

     2

- id: log-variable-fmtstring

     3

  patterns:

     4

    - pattern: log("...", $A)

     5

    - pattern-not: log("...", "...")

     6

  message: Variable passed as format string to logging

     7

  languages: [lua]

     8

  severity: ERROR

     9

- id: module-log-variable-fmtstring

    10

  patterns:

    11

    - pattern: module:log("...", $A)

    12

    - pattern-not: module:log("...", "...")

    13

  message: Variable passed as format string to logging

    14

  languages: [lua]

    15

  severity: ERROR

    16

- id: module-getopt-string-default

    17

  patterns:

    18

    - pattern: module:get_option_string("...", $A)

    19

    - pattern-not: module:get_option_string("...", "...")

    20

    - pattern-not: module:get_option_string("...", host)

    21

    - pattern-not: module:get_option_string("...", module.host)

    22

  message: Non-string default from :get_option_string

    23

  severity: ERROR

    24

  languages: [lua]