Disable/redirect/add noindex headers for .onrender.com URLs
in progress
A
Adam Quaile
When custom domains are active, provide an option to do one of the following:
* Disable the onrender.com subdomain
* Redirect it to one of the custom domains.
* Keep the site as-is but add a
noindex
header to all responses from the onrender.com subdomain. Benefits:
* Security [1]
* SEO [2]
----
[1] When using a custom domain one of the benefits is that instead of having the DNS pointing to Render, you can point it to Cloudflare (for example) as a proxy.
This reduces load on the origin server and the {project}.onrender.com seems like a bit of a loose-end.
Could somebody DDoS this server, bypassing cloudflare's protection?
(Similar to https://render.canny.io/features/p/add-option-to-redirect-the-onrendercom-subdomain-to-the-primary-custom-domain-fo)
[2] Add
x-robots-tag: noindex
header to deploys without assigned custom domains. This would allow testing one's full Web site content on Render without needing to alter a repo's existing "robots.txt" file yet avoid risking the duplicate-content penalty from Google and other search vendors. Similar functionality is provided by Vercel (https://vercel.com/docs/v2/edge-network/headers?query=robot#inlinecode).Log In
M
Matei Trandafir
Hi, maybe I'm missing something, but isn't this done? On my service on the settings page I found a checkbox next to custom domains to disable the default hostname, and it worked perfectly
Anurag Goel
in progress
M
Marius Gebhardt
Please make it possible to disable .onrender.com subdomains optionally. We are a Cloudflare Enterprise customer and use a O2O Setup so we proxy all traffic on our side. The onrender.com subdomain can not be proxied right now.
J
Jacob Ferraiolo
Any update on this?
p
philipp.faber
when will this be released? This is a must-have for moving away from aws.
D
David Geukers
Would love this
D
Daniel Meador
Frustrating to see something marked as "planned" 3 years ago. This does seem like a core item that is lacking
y
yaron levi
This is a huge hole for us security-wise.
Can't stress this enough.
When you pass your traffic via CloudFlare to audit, watch and block incoming routes, at the same time you are also open at the Render address which makes CloudFlare not relevant.
s
sys
It's mind boggling to me that this isn't available yet. Why do we have to try and convince you that it's insane to "just not publish it on the internet". Are we now supposed to set random project names, just so we can avoid being spammed by crawlers bruteforcing subdomains on *.onrender.com?
It's not a "convenience", it should be a given. We are spinning up servers and putting sites on the internet. How am I supposed to choose Render from the myriad of XaaS providers when we can't event control which domains can be used to reach our content?
Anurag Goel
Are there any use cases where you'd still need to index the subdomain if the custom domain is verified and active?
We can automatically disable indexing by adding the
X-Robots-Tag: noindex
header when you add and verify a custom domain.We will still need a way to permanently redirect the onrender.com domain to a custom domain.
T
T.J. Crowder
Anurag Goel: FWIW, I can't speak for anyone else, but I can't imagine wanting to have indexing on the
onrender.com
subdomain when I had a custom domain active.Load More
→