-
Notifications
You must be signed in to change notification settings - Fork 52
robots.txt is not being updated #719
Comments
Okay, I've tracked this down to the robots.txt file being special cased in the redirector. For the time being, I've manually replaced it with the one from stable. @pietroalbini -- looking at the lambda function we use, since it's on nodejs v8, we can't deploy updates to it without migrating to v10 or v12. I'm personally really worried about changing it in production anyway, that seems very prone to making a typo or whatever, but we should do so. Old one:
|
I would strongly prefer to avoid changing the lambda in production, as CloudFront has a ~5 minute delay when propagating changes. A while back I started porting doc.rlo and static.rlo to Terraform, applying the changes to dev-static.rlo and dev-doc.rlo. I think the best course of action will be to finish porting the dev- domains to Terraform, test the changes in dev-doc and then apply Terraform to the production distributions. |
I probably don't have time to finish that work and manually copying the robots.txt over once in a while doesn't seem too bad for the time being (we only really rarely update it anyway). |
This is now fixed. |
doc.rust-lang.org/robots.txt isn't getting updated, though /stable/robots.txt (and other URLs) are; those are however useless to my knowledge because crawlers only look in the root.
This is a follow up on rust-lang/rust#68677
cc @steveklabnik
The text was updated successfully, but these errors were encountered: