As I was the one who caused this by fixing `lein uberjar` :), I've submitted a pull request to ring which should fix improper `resource-response` behaviour: https://github.com/ring-clojure/ring/pull/97
2013 m. spalis 19 d., šeštadienis 04:02:06 UTC+3, xavi rašė: > > It seems it's this problem that somone else already reported a few days > ago... > > https://github.com/ring-clojure/ring/issues/96 > > > On Saturday, October 19, 2013 2:50:16 AM UTC+2, xavi wrote: >> >> If I comment out >> (wrap-resource "public") >> then it works (i.e. the uberjar produced by lein 2.3.3 serves the home >> page). >> >> Does this mean that the problem was not completely solved in Ring 1.2? >> Argh! I'll try to take a look to Ring's code and see if I can find the >> problem and fix it. >> On the other hand, why there's this difference in the uberjars generated >> by 2.3.2 and 2.3.3? >> >> Also, in case it may help, when requesting some other pages of the app, I >> get this error... >> >> 2013-10-19 02:17:33.219:WARN:oejs.AbstractHttpConnection:/password-resets >> java.lang.NullPointerException >> at java.io.FilterInputStream.close(FilterInputStream.java:155) >> at >> sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream.close(JarURLConnection.java:90) >> at ring.util.servlet$set_body.invoke(servlet.clj:94) >> at ring.util.servlet$update_servlet_response.invoke(servlet.clj:112) >> at ring.adapter.jetty$proxy_handler$fn__7145.invoke(jetty.clj:20) >> at >> ring.adapter.jetty.proxy$org.eclipse.jetty.server.handler.AbstractHandler$0.handle(Unknown >> >> Source) >> at >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) >> at org.eclipse.jetty.server.Server.handle(Server.java:363) >> at >> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483) >> at >> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:920) >> at >> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:982) >> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635) >> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) >> at >> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) >> at >> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628) >> at >> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) >> at java.lang.Thread.run(Thread.java:680) >> >> >> Xavi >> >> On Saturday, October 19, 2013 2:15:10 AM UTC+2, Phil Hagelberg wrote: >>> >>> >>> xavi writes: >>> > @Phil I'm already using ring 1.2 >>> >>> Hm; it's probably the same problem manifested a different way >>> then. Something is assuming that any entry in a jar file is fair game >>> whether it's a directory or file. >>> >>> -Phil >>> >> -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
