Skip to content

Latest commit

 

History

History
190 lines (132 loc) · 4.45 KB

CHANGES.md

File metadata and controls

190 lines (132 loc) · 4.45 KB
Raw

Release notes

Notable changes will be documented here

0.9.37

  • limiting processing the response body via limitBodyToNBytes when searchForBodyPatterns==true
  • upgraded dependencies
  • Go v1.23

0.9.36

  • upgraded dependencies
  • Go v1.22

0.9.35

  • upgraded dependencies
  • link-checker-service
    • token validation via JWKS

0.9.34

  • upgraded dependencies

0.9.33

  • Go v1.21

0.9.32

  • Go v1.20

0.9.31

  • Go v1.19
  • link-checker-service
    • tracking domain stats as blacklist input
    • domains of URLs are parsed and used in the domain blacklist without the port
  • sample UI:
    • showing detailed domain stats

0.9.30

  • link-checker-service
    • counting cache hits and misses

0.9.29

  • link-checker-service
    • sanitizing log lines that include API user input

0.9.28

  • link-checker-service
    • a simple /stats endpoint
  • sample UI:
    • showing the /stats results

0.9.26

  • Go v1.17
  • Build & Release via GitHub Actions

0.9.25

  • better docker image name

0.9.24

  • publishing docker images
  • link-checker-service
    • echoing the Go version

0.9.23

  • upgraded the dependencies
  • link-checker-service
    • default ristretto back to false
    • do not echo config file location implicitly
    • fixed golint warnings & go fmt

0.9.22

0.9.21

  • link-checker-service:
    • tracing the elapsed time in total per URL and per URL checker plugin (elapsed_ms response fields)
    • tracing the error message from each URL checker plugin
  • sample UI:
    • exporting the elapsed total time to CSV
    • exporting the URL checker plugin trace as a JSON blob to CSV

0.9.20

  • link-checker-service:
    • a new URL checker plugin: urlcheck-pac, configured via pacScriptURL for more complex proxy scenarios
    • more reasons to retry a check with a different checker plugin added
    • checker plugins are now traced in the check_trace field of the URLStatusResponse

0.9.19

  • link-checker-service:
    • JWT authentication
      • allow credentials in CORS
      • configurable LCS_USEJWTVALIDATION, LCS_DISABLEREQUESTLOGGING
      • logging the configuration before validating it
    • configurable sequence or URL checker plugins, e.g. with and without using a proxy
    • logging GOMAXPROCS on serve
    • the simplest health & liveness check + version endpoints are now unauthenticated and not rate-limited

0.9.18

  • link-checker-service:
    • Simple authentication via JWT validation

0.9.17

  • link-checker-service:
    • HTTP BadRequest on empty request
  • sample UI:
    • abort button

0.9.16

  • link-checker-service:
    • use the browser user agent in the last resort get request
    • cache failed DNS resolution to not block the other requests
    • total request timeout increased

0.9.15

  • link-checker-service:
    • better feedback when reading in config files
    • fixed DNS resolution for URLs with an explicit port

0.9.14

  • link-checker-service:
    • best effort remote address resolution
  • sample UI:
    • show the remote address resolution in the results
    • added a remote_addr column to CSV export

0.9.13

  • link-checker-service:
    • optional: resolve remote addresses
  • sample UI:
    • disable the CSV download button on no check status
    • configurable service URL in the sample UI

0.9.12

  • new release packaging

0.9.11

  • link-checker-service:
    • serve -a <addr> allows customizing the bind address, e.g. localhost-only: 127.0.0.1:8080

0.9.10

  • binaries: link-checker-service, sample UI, sample large list check
  • link-checker-service:
    • configurability
    • response-specific caching of results
    • aborting processing on client disconnected
    • rate limiting per domain
    • concurrency limit
    • rate limiting per client
    • optional domain blacklisting using glob patterns
    • Docker deployment
    • URL de-duplication in the request, and duplication in the response
    • optional searching for patterns in HTTP response bodies
    • streaming responses as they arrive
  • sample UI:
    • CSV export
    • synchronous and asynchronous requests
    • filtering by status
    • hiding successes