<p></p>
<p>This change has been made and I am closing this issue as complete.</p>
<h2>Before the change</h2>
<pre><code>$ curl -I https://docs.bisq.network
HTTP/2 200
[...]
server: Netlify
</code></pre>
<pre><code>$ curl -I http://docs.bisq.network
HTTP/1.1 301 Moved Permanently
[...]
location: https://docs.bisq.network/
server: Netlify
</code></pre>
<h2>After the change</h2>
<pre><code>$ curl -I https://docs.bisq.network
HTTP/2 301
[...]
location: https://bisq.wiki
server: cloudflare
</code></pre>
<pre><code>$ curl -I http://docs.bisq.network
HTTP/1.1 301 Moved Permanently
[...]
Location: https://bisq.wiki
Server: cloudflare
</code></pre>
<h2>Notes on changes to Cloudflare and DNS</h2>
<p>This change involved setting up the following page rule at Cloudflare:</p>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/301810/121994588-d4e4e280-cda5-11eb-8c14-440748927d12.png"><img width="1041" alt="image" src="https://user-images.githubusercontent.com/301810/121994588-d4e4e280-cda5-11eb-8c14-440748927d12.png" style="max-width:100%;"></a></p>
<p>And to make the page rule take effect, it was necessary to start proxying DNS for docs.bisq.network through Cloudflare. Previously, DNS was un-proxied.</p>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/301810/121994640-eb8b3980-cda5-11eb-9fc2-e8bb909c6e8c.png"><img width="1047" alt="image" src="https://user-images.githubusercontent.com/301810/121994640-eb8b3980-cda5-11eb-9fc2-e8bb909c6e8c.png" style="max-width:100%;"></a></p>
<h2>Notes on using a 301 redirect</h2>
<p>I've opted to use a 301 (Permanent) redirect vs. a 302 (Temporary) redirect here, as my understanding is that 301s are better for search engine optimization, i.e. transferring ranking juice from docs.bisq.network to bisq.wiki. The potential downside of this approach is that if we were to bring docs.bisq.network back up, clients who had already received the 301 would keep the redirect cached and would not see that docs.bisq.network is actually back up and serving its content. This scenario seems unlikely, though, so just mentioning it here for completeness.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq-docs/issues/210#issuecomment-861168877">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNXIPWQDEF6YDYQTXULTS3MNRANCNFSM46WOUCHQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNSHIDFMXPL7RD3DE7TTS3MNRA5CNFSM46WOUCH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGNKGJ3I.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq-docs/issues/210#issuecomment-861168877",
"url": "https://github.com/bisq-network/bisq-docs/issues/210#issuecomment-861168877",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>