@ddellacosta: I agree that DECODE_URL should be false. I suspect that was a change in undertow that slipped past us

what type of data did you have that failed when decoded twice?

@tcrawley: pretty simple really, we have some params that are strings containing %—when these got re-decoded by compojure further down the chain, it blew up

@brenden: did you ever solve your issue? adding listeners should be fine as long as they get their own port.

@jcrossley3 sort of, I ended up writing it as a ring middleware instead. I needed to chain together the ring and undertow handlers to be listening on the same port, but I guess that's not feasible.

@brenden: it should be feasible, but may require some careful nesting of your ring stack within your HttpHandler stack. it's only recently that we made it easier to construct the latter with https://github.com/immutant/immutant/blob/master/web/src/immutant/web/undertow.clj#L28

but i'm glad you got things going

it was possible before, but only using "internal" namespaces