#11

ring.middleware.params: Use keywords for param keys

The protocol between ring.middleware.params and compojure routes appears to have drifted since your blog post was authored. The example code demonstrates definition of a route with parameters defined as ...

  • Opened by ndimiduk Feb 6, 2011
  • 1 comment
#12

Add another handler body type: callback

Hi! I have a scenario, where I want to return a result of XSLT transformation (that's XML templating). I'm using a Saxon processor, which accepts OutputStream (or Writer) and serializes a formatted ...

  • Opened by lolownia Feb 21, 2011
  • 1 comment
#13

add mime-type

Hi, I wanted a mime-type of ".htc" and after googled I found that there are a lack of mime-types in default-mime-type. So I added all mime-types which is not in default-mime-type. I used following ...

  • Opened by hozumi Mar 9, 2011
  • 5 comments
#14

second attempt at cache-control middleware

This patch adds a middleware for setting HTTP headers, and specifically setting the cache-control headers. I made a first attempt at this last September, weavejester had comments on my patch, sorry it ...

  • Opened by arohner Apr 5, 2011
  • 3 comments
#15

Stacktrace changes

The current stacktrace middleware improperly nests the html <body> in it's <head> tag. Additionally, it does not include the causes of an exception, only the topmost exception ...

  • Opened by youngnh Apr 6, 2011
  • 1 comment
#16

properly structure stacktrace html

fix to correctly nest html generated by wrap-stacktrace middleware

  • Opened by youngnh Apr 7, 2011
  • 1 comment
#17

Stacktrace with Full Exception Causes

Adds all causes of an Exception to the returned html of a wrapped stacktrace.

  • Opened by youngnh Apr 7, 2011
  • 3 comments
#18

include Exception causes in stacktrace

for more complete reporting on errors

  • Opened by youngnh Apr 12, 2011
  • 1 comment
#19

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" ...

#20

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.