Infra would be the best to get these questions asked.

On Wed, Mar 7, 2018 at 9:52 AM Aaron Markham <aaron.s.mark...@gmail.com>
wrote:

> Ah ok thanks! We will try it out.
> Regarding log access or reporting on logs, is that available? Would like
> some more capability on spotting 404s, and doing reverse dns reporting so
> we can track organization level traffic.
>
> Cheers,
> Aaron
>
> On Mar 7, 2018 04:13, "John D. Ament" <johndam...@apache.org> wrote:
>
>> .htaccess support should still work.  I would recommend following up with
>> infra if you're seeing something not quite right.
>>
>> John
>>
>> On Wed, Mar 7, 2018 at 1:54 AM Hen <bay...@apache.org> wrote:
>>
>>> Apologies for my rustiness :(
>>>
>>> Are we still able to manage a mod_rewrite configuration per project, or
>>> did
>>> that go away?
>>>
>>> Thanks,
>>>
>>> Hen
>>>
>>> ---------- Forwarded message ----------
>>> From: Aaron Markham <aaron.s.mark...@gmail.com>
>>> Date: Mon, Mar 5, 2018 at 3:54 PM
>>> Subject: 404 issues
>>> To: d...@mxnet.incubator.apache.org
>>>
>>>
>>> I've been notified by several parties about 404s for files that are
>>> now longer available on the site.
>>> https://github.com/apache/incubator-mxnet/issues/9917
>>>
>>> This page returns 404:
>>> https://mxnet.incubator.apache.org/api/python/module.html
>>>
>>> It was moved here:
>>> https://mxnet.incubator.apache.org/api/python/module/module.html
>>>
>>> There are many other examples of moved content. Some are temporarily
>>> "fixed" via adding a meta-refresh tag in the html source for the old
>>> pages. For example the meta tag is being used to redirect to faq, the
>>> new location for the how_to docs.
>>>
>>> It would seem a better solution for us is to use htaccess files and
>>> publish persistent redirects for the new location(s) of content.
>>>
>>> Do we have a way of pushing a config to the Apache infra to facilitate
>>> this? I think we'd need config access if we're to put up some custom
>>> 404 pages too (which would be nicer than what we have now.)
>>>
>>> Also, is there a good way to access the log files to get a better idea
>>> of the 404 situation?
>>>
>>> Cheers,
>>> Aaron
>>>
>>

Reply via email to