<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I think that making it so we can do redirect is good. The
current blackhole approach is less than desirable.</p>
<p>Jay<br>
</p>
<br>
<div class="moz-cite-prefix">On 7/27/2017 10:06 PM, ChangBo Guo
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANWmB0Wdd42Rc3J6p=94hK+Gb30qKNRtGCE--AgTOMCZ6VfBqw@mail.gmail.com">
<div dir="ltr">++ for the solution.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-07-28 2:24 GMT+08:00 Doug Hellmann
<span dir="ltr"><<a href="mailto:doug@doughellmann.com"
target="_blank" moz-do-not-send="true">doug@doughellmann.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts
from Jeremy Stanley's message of 2017-07-27 16:40:08 +0000:<br>
<span class="">> On 2017-07-27 12:23:39 -0400 (-0400),
Sean Dague wrote:<br>
> > In the #openstack-nova channel this morning we
were debugging some cells<br>
> > v2 things, and ran into the fact that the online
docs for this -<br>
> > <a
href="https://docs.openstack.org/nova/latest/cells.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://docs.openstack.org/<wbr>nova/latest/cells.html</a>
go to a 404. That's a<br>
> > previously well known link, people have it in
their browser history,<br>
> > bookmarks, wiki pages, other websites.<br>
> ><br>
> > My understanding of big moves like this is that
redirects are important.<br>
> > Things going blackhole like that not only is an
inconvenience to users,<br>
> > but impacts our search engine rankings, and
takes a while for them to<br>
> > all sift out. I know in sites I run I'm still
regularly getting in<br>
> > bounds to paths on the site that haven't been
there for 8 years.<br>
> ><br>
> > It would be really good if we had a way (manual
or automated) to have<br>
> > 301 redirects, that are fixable by the teams
that now own the<br>
> > documentation (the project teams).<br>
><br>
> We can look at including .htaccess files in the tree
I guess? Or<br>
> some metadata the publish job uses to build them
maybe?<br>
<br>
</span>That's exactly what I was thinking.<br>
<br>
1. Enable .htaccess files by turning on allowoverride for<br>
<a href="http://docs.openstack.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">docs.openstack.org</a>.<br>
<br>
2. Add .htaccess files in each tree, as needed (see<br>
<a href="https://review.openstack.org/487932"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://review.openstack.org/<wbr>487932</a>
for an example of how this<br>
is done with sphinx).<br>
<br>
3. Update the main .htaccess file in openstack-manuals to
redirect<br>
from the old location of docs in a way that passes the
full path.<br>
Right now we redirect to /project/latest/:<br>
<br>
redirectmatch 301 "^/developer/([^/]+)/.*$"
/$1/latest/<br>
<br>
I think that would change to look something like:<br>
<br>
redirectmatch 301 "^/developer/([^/]+)/(.*)$"
/$1/latest/$2<br>
<br>
We would only want to do that for projects that actually
have<br>
.htaccess files, so we can put a flag in the project-data
files in<br>
openstack-manuals and generate project-specific redirect
rules (we're<br>
already doing that for some other pages).<br>
<br>
Then when someone visits docs.o.o/developer/nova/cells.<wbr>html
it would<br>
redirect to docs.o.o/nova/latest/cells.<wbr>html. The nova
team then<br>
need to have a redirect from docs.o.o/nova/latest/cells.<wbr>html
to<br>
docs.o.o/nova/latest/user/<wbr>cells.html.<br>
<br>
If folks think that's a good approach, I will start on the
patches<br>
needed in infra and openstack-manuals (1 and 3).<br>
<span class="HOEnZb"><font color="#888888"><br>
Doug<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>ChangBo Guo(gcb)</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>