This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-20
Channels
- # beginners (43)
- # boot (44)
- # chestnut (17)
- # cider (78)
- # cljs-dev (24)
- # cljsrn (16)
- # clojure (84)
- # clojure-dusseldorf (1)
- # clojure-italy (21)
- # clojure-losangeles (2)
- # clojure-russia (140)
- # clojure-sg (2)
- # clojure-spec (8)
- # clojure-uk (16)
- # clojurescript (23)
- # cursive (7)
- # datascript (1)
- # datomic (18)
- # docker (20)
- # ethereum (1)
- # fulcro (16)
- # garden (4)
- # graphql (27)
- # hoplon (9)
- # jobs (4)
- # luminus (34)
- # off-topic (6)
- # om (4)
- # onyx (35)
- # pedestal (3)
- # re-frame (24)
- # ring-swagger (15)
- # rum (6)
- # shadow-cljs (22)
- # spacemacs (8)
- # specter (22)
- # yada (7)
I'm having some difficulties with yada's 'if-modified-since' capabilities. In the browser it works fine. But when I send it via an aleph http client with the same exact string as the one received with 'last-modified', the server still sends me the whole response instead of a 304.
Could it be that the coercion of java.util.Date to the 'last-modified' string is less precise (resolution of seconds) and can thus appear to be a different time when I send it back?
I think that's it https://github.com/juxt/yada/blob/0a8cd0a1790db6885f835e847bba80796d4f7f79/src/yada/interceptors.clj#L215
Possibly. HTTP time resolution is seconds as far as I recall from the spec Can you raise an issue?