Re: Response content type when url has no extension

Hi, On Wed, Jun 22, 2016 at 4:19 PM, Jason Bailey wrote: > ...Under > org.apache.sling.servlets.resolver > for the property servletresolver.defaultExtensions ... This is not for the use case discussed here, as explained in that parameter's OSGi config description:

Re: Response content type when url has no extension

On Wednesday 22 June 2016 14:15:42 Bertrand Delacretaz wrote: > Hi, > > On Wed, Jun 22, 2016 at 12:39 AM, Ben Fortuna wrote: > > ...Should this be handled in sling or is it common practice to use another > > mechanism to redirect / to /index.html? ... > > I suspect people

RE: Response content type when url has no extension

ers@sling.apache.org> Subject: Re: Response content type when url has no extension Hi, On Wed, Jun 22, 2016 at 12:39 AM, Ben Fortuna <benfort...@gmail.com> wrote: > ...Should this be handled in sling or is it common practice to use > another mechanism to redirect / to /index.html? ...

Re: Response content type when url has no extension

Hi, On Wed, Jun 22, 2016 at 12:39 AM, Ben Fortuna wrote: > ...Should this be handled in sling or is it common practice to use another > mechanism to redirect / to /index.html? ... I suspect people often use front-end rewriters like mod_rewrite to add extensions to URLs

Re: Response content type when url has no extension

Hi Ben, On Wed, 2016-06-22 at 08:39 +1000, Ben Fortuna wrote: > Hi, > > Just wondering what is the standard practice for managing sling > requests > with no extension. My use case is that my index node is called > 'index' so > when I get a request for just the domain name root (ie. >