Hi, Best wishes for 2016!
Does anyone know why mod_dir doesn't generate a Content-Location header when a URI ending in "/" is requested? This is a behavior that is common in 2.2 and 2.4. For some publishing tools, it's useful to know what's the actual URI that's mapped to "/" thru DirectoryIndex. I can contribute time to propose a patch that does this. I can either add this as an in-built feature to mod_dir with configuration options to disable it or as an optional hook tha's called once there's a positive match for a DirectoryIndex entry. Any comments? Thanks! -jose
