On 7 February 2013 16:37, larry google groups <lawrencecloj...@gmail.com>wrote:
> Okay, got all this working. Thank you very much for your tip. Can you say > what you think the problem was? I noticed that the wrap-resource middleware didn't account for the HTTP HEAD method, while route/resources does. According to the HTTP specification, a HEAD request to a URI should return the same status and headers as a GET request to the same URI. My guess is that sometimes, instead of sending a GET directly, the browser sends a HEAD, perhaps to check the Last-Modified date or ETag. The HEAD request would erroneously return a 404. I'll mark this as an issue in Ring and get it fixed. - James -- -- 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.