Clojurians Log v2

@tcrawley: https://gist.github.com/trancehime/eabce83bce9eb849aa8c here is the gist of the stack trace. It's the same error for every single static file in the WAR deployment, so I'm just putting it in the gist once

@trancehime: odd, there is no immutant code in that stack. how are you deploying your servlet?

I suspect if you (require 'immutant.web.internal.ring), your problem will go away, since that's what triggers the defmethod call for vfs: urls

and that must not be happening with whatever code path you are using

we should probably move that trigger to another namespace to cover cases where the ring ns doesn't get loaded

hmm, are you creating your war file with lein immutant war, or some other method?

Yes, I am using lein immutant war

howdy!

Hallo~

our timezones align!

Yes, it surely is inconvenient that I am located in Asia :^)

let's say it's inconvenient that I'm located in the US :)

how are you deploying your servlet within your :main?

Wait, hold on a second. I think there is a miscommunication

The stack trace has no immutant code in it because it wasn't made using Immutant, I got mixed up with a separate web app that I am actually building with lein immutant war which has a totally different issue (I'm getting 403 errors)

ah, for the non-immutant app, you'll need to copy https://github.com/immutant/immutant/blob/master/web/src/immutant/web/internal/ring.clj#L155-L171 into your app, since WildFly will give you :vfs urls, and ring won't understand those

except you won't have try-resolve, since that's an immutant fn

Hmm. I see

Interestingly, the webapp I built with lein immutant war seems to produce no errors upon deployment, but when I try to access it, I get 403 errors. Which realy confused me. Then again it's being fronted by nginx. So I dunno

but try-resolve is pretty simple: https://github.com/immutant/immutant/tree/master/core/src/immutant/internal/util.clj#L61

can you try accessing it directly (bypassing nginx)?

I was unable to

can you access it from the machine it is running on via curl?

I can't try that right now but if I could, what would that mean?

if you can curl routes in WildFly and not get a 403, that would point to a misconfiguration in nginx I'd think

Hmm. Okay

Thanks for your patience and everything

I'm happy to help!

It's a big deal for me 😃