Re: Why 301 permanent redirect with appended slash?

2019-08-01 Thread 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

Re: Why 301 permanent redirect with appended slash?

2019-07-31 Thread J. Lewis Muir
On 07/31, Francis Daly wrote: > On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote: > > Hi there, > > > I have a minimal nginx.conf with one server block that sets the root > > directory and one location with a prefix string of "/foo/", and for a > > request of "/foo", it returns a

Re: Why 301 permanent redirect with appended slash?

2019-07-31 Thread Francis Daly
On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote: Hi there, > I have a minimal nginx.conf with one server block that sets the root > directory and one location with a prefix string of "/foo/", and for a > request of "/foo", it returns a 301 permanent redirect to "/foo/". Why? > I

Why 301 permanent redirect with appended slash?

2019-07-30 Thread J. Lewis Muir
Hello, all! I have a minimal nginx.conf with one server block that sets the root directory and one location with a prefix string of "/foo/", and for a request of "/foo", it returns a 301 permanent redirect to "/foo/". Why? I expected it to return 404 or similar. I also tried a prefix string of