On 03/08/2017 10:31 AM, Daniel P. Berrange wrote:
> On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote:
>> Hey all,
>>
>> We have a set of old vanity redirect URLs from back when we made a URL
>> for each project:
>>
>> cinder.openstack.org
>> glance.openstack.org
>> horizon.openstack.org
>> keystone.openstack.org
>> nova.openstack.org
>> qa.openstack.org
>> swift.openstack.org
>>
>> They are being served from an old server we'd like to retire. Obviously,
>> moving a set of http redirects is trivial, but these domains have been
>> deprecated for about 4 now, so we figured we'd clean house if we can.
>>
>> We know that the swift team has previously expressed that there are
>> links out in the wild pointing to swift.o.o/content that still work and
>> that they don't want to break anyone, which is fine. (although if the
>> swift team has changed their minds, that's also welcome)
>>
>> for the rest of you, can we kill these rather than transfer them?
> 
> Does the server have any access log that could provide stats on whether
> any of the subdomains are a receiving a meaningful amount of traffic ?
> Easy to justify removing them if they're not seeing any real traffic.
>
> If there's any referrer logs present, that might highlight which places
> still have outdated links that need updating to kill off remaining
> traffic.

Yes. The majority of the hits are from search engines, fwiw. :)

However, we're also changing the current redirect from temporary to
permanent, so we're hoping that'll get the search engines to fall over
to the other thing.

I agree, doing that for a while, especially after having gotten the
redirect changed and landing the patches to remove references from our
docs should give us better info on where we stand currently.


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to