Why 301 permanent redirect with appended slash?

[Francis Daly]

On Wed, Jul 31, 2019 at 11:45:58AM -0500, J. Lewis Muir wrote:
> On 07/31, Francis Daly wrote:
> > On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote:

Hi there,

> > As in: your request for "/foo" does not match any location{}, and so is
> > handled at server-level, which runs the filesystem handler and returns
> > 200 if the file "foo" exists, 301 if the directory "foo" exists, and
> > 404 otherwise.
> 
> Yes, thank you very much for the explanation!  That all makes sense.
> I couldn't find this behavior documented anywhere; is it documented
> somewhere that I've missed?

I've not looked much for documentation on what nginx's filesystem handler
does recently, mostly because it seems to do what I expect.

https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/

seems to describe some of the above.

Cheers,

	f
-- 
Francis Daly        francis at daoine.org