given that it can be a bit tricky to properly determine what the "real" remote ip of the client is, does yada provide a mechanism for this ? there is of course :request :remote-addr, but then also the x-forwarded-for headers, which can in turn contain multiple ip addresses separated by a comma

https://github.com/ring-clojure/ring-headers/blob/master/src/ring/middleware/proxy_headers.clj is the ring one

You always want to count from the end of the remote-addr list, not the front

as the client controls what gets put on the front

depending on how many layers of proxies you have you slice the last or second to last off

(as you probably are already aware)

@lmergen yes, there is an interceptor that determines the correct one and fishes it out into the ctx. Of course, the entire Ring request is available as :request in ctx so you can use Ring middleware too

ah where can i find that interceptor ? I tried searching a bit through the repo but couldnt find anything useful

noob question please: I'm attempting to add yada to an existing project, with a simple test route. Whether with bidi or compojure, I'm seeing an error when compiling:

java.lang.ClassNotFoundException: io.netty.channel.epoll.Epoll, compiling:(aleph/netty.clj:1:1)
...

@limist you're getting the wrong version of netty I think. You've probably got dependency conflicts.

@limist https://github.com/technomancy/leiningen/issues/1055 This came up on Google, on mobile else I'd type up most of it :)