nitpicking, but the missing "ring/" broke my stride
.. I found my pace pretty fast though. A beginner might not have.
- Inline CSS should be in a resource - Use new Hiccup functions like html5 - Update the set of ring keys.
Create a charset function that adds or changes the charset of a response.
run-jetty :configurator set to run last
This change allows for replacing the default proxy-handler with a custom handler; the benefit of this (for us) was to allow for logging custom timing and request information from the handler in a way that ...
Add some new middleware that proxies HTTP HEAD requests as GETs and the removes the body from the response. This will make it easier to support the HEAD method in Ring apps.
Functions for piped output streams
Create a new namespace, ring.util.io in ring-core. The namespace should have: - Functions for turning an OutputStream into an InputStream - Copy ring.util.test/string-input-stream into ring.util.io ...
Cookies support clj-time intervals and dates
In ring.middleware.wrap-cookies: - The :max-age key should support JodaTime Intervals (via clj-time) - The :expires key should support JodaTime DateTimes and Java Dates Existing Ring 1.0 behaviour ...
Tag all public functions with version metadata
Public functions should have {:added "1.0"} metadata to define which version they were added in.
Cookie parsing needs to deal with nil return value from url-decode
The decision to allow url-decode to return nil for improperly encoded strings (instead of throwing an exception) now means that cookie handling needs to accomodate this newly-endorsed return value. Frankly, ...