Carlos Fontes

When I was cleaning my forks, I accidentally deleted the one where the fix was made, but the source is still in clojars. I think It was a trivial fix...

@pharcosyle I cannot reproduce your success with Clojure 1.5.1. I still have this error:  Do you also have warning error with `lein cljsbuild...

I'm sure, but maybe it's possible I got the same warning for a different reason.

@pharcosyle, unfortunately I'm not using Clang anymore in this project.

Thanks. I just fixed the lexical error, and added a missing helper function. `wrap-insecure-redirect` serves to make a permanent redirect from `https` to `http`. The purpose is that from then...

Furthermore, If I used `wrap-hsts` and `wrap-ssl-redirect` before, and then replace that with just `wrap-insecure-redirect`, after the first request, typing `https://site.com` will be rewritten to `http://site.com` in Chrome, Firefox and...

I mean "first request" above as a request made after the request that was used by `wrap-expire-hsts` or `wrap-expire-hsts` the first time, independent of the browser session.

Thanks, I didn't remember `max-age` was an option . To be clear, that code is just to give an example for the use case. In no way I mean that...

Did anyone find a solution to the `index.html` redirect problem? In my case `/service-name` is redirected to `/index.html`, yet I can find the resource at `service-name/index.html`.

lgtm to have the option, but maybe hitting a backend server to handle requests to OpenAI should be the default with option to override with direct request to OpenAI instead....