Clojurians Log v2
pedestal 2025-09-12
So if you've tried out 0.8.0-rc-3 in production, please be in touch; I really need the feedback before we jump to the final release.
fwiw, http://cljdoc.org is using rc-3 in prod. Have not noticed any issues!
I tried updating an old program and was surprised by a quirk of routing. The routing table included a path "/foo/". The terminal "/" is significant because it establishes the base URL for relative references. Anyway, the new default router served that page in response to requests for "/foo" and rebuked requests for "/foo/" with a 404. Choosing a different routing strategy restored the expected behavior. I had expected the routing strategies to affect only efficiency and disambiguation of conflicting fixed/parameter options.
I'm surprised to see that URLs ending with a slash work; they should not end with a slashk, but could end with .../foo/*path to set a :path path-param to the remaining path after /foo/.
RFC3986, section 3.3, explains that the last of the /-separated segments of a URL can be empty. Section 5.2.3 explains that relative references are resolved as "the reference's path component appended to all but the last segment of the base URI's path". Together, it is by those rules that, on the page at URL foo/ (see the empty final path segment), the web browser resolves an href of baz to foo/baz; and on the page at URL foo (non-empty final path segment) the browser resolves an href of baz to baz. A website can be constructed one way or the other. The URLs foo and foo/ are not the same, and are both valid, and cause the browser to resolve relative references differently, so Pedestal would be expected to accommodate both in routing. Er - interesting about the *path kludge, but it would be infelicitous in a case where no parameter was expected there.
Yes, that's how borwsers and servers see URLs, but in the routing table, we're defining dispatch rules, so it's not quite the same thing.
I also was looking for an example of using pedestal-jetty (especially the detail of customizing the "http configuration" of Jetty's various obscure limits). But the examples I found in git dated from the era of Pedestal 0.5.9.