I migrated a web app backend to Jetty 12 and I changed ring adapter to info.sunng/ring-jetty9-adapter
:ssl-client-cert now returns an array of certificates. It used to be single certificate. ![]()
Do you know any other potential issues or discrepancies?
I migrated a web app backend to Jetty 12 and I changed ring adapter to info.sunng/ring-jetty9-adapter
:ssl-client-cert now returns an array of certificates. It used to be single certificate. ![]()
Do you know any other potential issues or discrepancies?
I’m curious which Ring adapter you were using before?
At work, we used the SunNg adapter for a while, until Ring itself updated the Jetty version it used. Then we switched back to Ring – using Jetty 12 and WebSockets.
Ring doc says they are still using Jetty 9: https://cljdoc.org/d/ring/ring-jetty-adapter/1.15.3/api/ring.adapter.jetty
Jetty 9 went End of Life (EOL)
Ring updated from Jetty 9 ages ago. The docstring hasn’t been updated.
See ring/ring-jetty-adapter/project.clj at master · ring-clojure/ring · GitHub and you can see it is using Jetty 12.1.0 right now.
See also the CHANGELOG: ring/CHANGELOG.md at master · ring-clojure/ring · GitHub Ring updated from Jetty 9 to Jetty 11 about two and a half years ago (and to Jetty 12 about a year ago).
I created a GH issue to get that ns docstring fixed: Docstrings still refer to Jetty 9 · Issue #545 · ring-clojure/ring · GitHub