Hi, I'm using duct to serve a fulcro webapp and I want to alias "/" as "/index.html" so it's served as a static route. I've tried using the following configuration keys:

:duct.middleware.web/route-aliases {"/" "/index.html"}
:duct.core/handler {:middleware [#ig/ref :duct.middleware.web/route-aliases]}

http :3000

http :3000/index.html

I can’t see anything obviously wrong with that. What does (pprint (:duct.core/handler config)) look like?

^ @tobias291

{:middleware [#ig/ref :duct.middleware.web/route-aliases
              #ig/ref :duct.middleware.web/not-found
              #ig/ref :duct.middleware.web/webjars
              #ig/ref :duct.middleware.web/defaults
              #ig/ref :duct.middleware.web/log-requests
              #ig/ref :duct.middleware.web/log-errors
              #ig/ref :duct.middleware.web/stacktrace],
 :router #ig/ref :duct/router}

and

(pprint (:duct.middleware.web/route-aliases config))

{"/" "/index.html"}

Hm. I don’t see anything wrong with that, either…

What happens when you go to “/”?

Oh, actually, I do see the problem.

If the index page is static, then it will be served by wrap-resource in the defaults middleware before the route-aliases are reached.

So:

{:middleware [#ig/ref :duct.middleware.web/not-found
              #ig/ref :duct.middleware.web/webjars
              #ig/ref :duct.middleware.web/defaults
              #ig/ref :duct.middleware.web/route-aliases]}

By putting the references in directly, you can explicitly specify the order.

@weavejester Thanks! just tried that and it works perfectly 🙂

No problem! I’ve been thinking about a more sophisticated way of ordering middleware, but it’s always a tradeoff.