You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for configuring static files/directories with appsettings.json just like how nginx allows it.
The key can be default Address or it could be named Path to seperate it.
Nginx also allows to specify an index file like index index.html; this could also be used as another value "Index": "index.html"
This is tangential to YARP's primarily concern as a library for routing to external sources. We do consider static file config important in the pre-built exe scenario that would be comparable to nginx.
I don't envision this as being part of the cluster config, none of the cluster settings make sense for static assets. I expect it would use a different config section entirely.
What is missing here (possibly more from ASP.NET than YARP) is a standard config section for configuring static files. In the same way that you add the config provider to YARP, it would nice to be able to specify a config section that would map to a StaticFileOptions instance enabling the configuration of folders, headers, auth, content types etc from config rather than code.
Not that difficult to write, but probably not a high priority for YARP v1.
Add support for configuring static files/directories with appsettings.json just like how nginx allows it.
The key can be default
Address
or it could be namedPath
to seperate it.Nginx also allows to specify an index file like
index index.html;
this could also be used as another value"Index": "index.html"
The text was updated successfully, but these errors were encountered: