HttpFileService could provide more options related to trailing slash

I was trying to clean up code using the new file service capabilities (removing hacky path mapping to redirect everything to index.html for example) but found I can’t remove all my hacks since we use “clean URLs” without a trailing slash to read index.html for that page. The current HttpFileService will read index.html for requests that end with / but not otherwise. Adding an option to HttpFileServiceBuilder that allows URLs without an extension to have slash added before resolving the file would make this simpler.

For reference, firebase’s related setting https://firebase.google.com/docs/hosting/full-config#control_trailing_slashes

[anuraaga]

Thanks for checking the behavior! It sounds like they follow armeria’s current behavior then. I guess I’ll add a flag, and it’s basically similar to doing this sort of config in nginx when needing slash-less URLs - https://stackoverflow.com/a/31189870

[trustin]

nginx and Apache HTTPd at least seem to send a redirect response when a client sent a request to a directory without a trailing slash (empty-to-slash), which matches the current HttpServerHandler behavior. I guess this kind of redirection is common for directories.

However, they indeed don’t send a redirect when showing an index file. That being said, I guess we can:

• keep the current HttpServerHandler behavior as-is
• make HttpFileService redirect for empty-to-slash cases while serving an index file without redirection

Additionally, we might want to add some configuration property to Server, like TrailingSlashPolicy if we need more flexibility?