0.2 Fixing an issue with response body as InputStream
When the response body is an InputStream that gets copied to the response's OutputStream, if the OutputStream gets broken (e.g., the client interrupts the transfer), the InputStream will not get closed ...
Set default character encoding for response to UTF-8
Hello! I recently started to develop a web-application using ring and jetty and faced a problem with non-english content: letters in server response were substituted for question marks. Setting "character-encoding" ...
Here's a fix for the wrap-params issue
I played around with several variations of this, but in the end it seems best to just fall out to nil when it can't decode a parameter. I tried this by patching the jar in place on my project and ...
Fix for wrap-nested-params and multi-valued parameters without '[]'
I recently had to use a multiple select box on an HTML form, but didn't end the parameter name with "[]". wrap-params correctly transforms "foo=bar&foo=baz" into {"foo" ...
Set character encoding for response according to 'charset' field of 'Content-Type' header
Hello again! This is fixed fix for my last pull request. Hope I'm doing this right. Regards, Nick.
Make Jetty SSL Connector respect :host option
In ring.adapter.jetty/run-jetty, the :host option is used for the non-SSL Connector, but not for the SSL Connector. This means that the SSL Connector binds to 0.0.0.0 even if :host is set, which is unexpected ...
not idiomatic, but ring is executed by every request and response.
Make sure regexp is performed against a string.
Make sure regexp is performed against a string. This helps the rare case where keyword params already exist at this point.