Hi Paul, I understand the problem. I'm not saying "don't add the '/' at the > end"; I'm saying have a flag that silently adds it internally without > doing an explicit redirect. In the cases where you set > directoryRedirection to true, mutate the Request instead to append > the '/' as if you did the redirection and the client sent you back a > new request with the trailing '/'.
But doing the redirection internally only wouldn't help for the issue mentioned above. The problem is that it is the browser that resolves the relative URI, so if he doesn't know the actual/recommended directory URI, how can he guess that a trailing '/' must be appended before the relative part ? Best regards, Jerome
