Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why can't I add this HTTP header to my blobs?
See original GitHub issueI just learned that Googlebot-Image has been indexing images at my site, presumably because a robots.txt entry is only honored for LOCAL images … those served from the site’s domain. Images that are in Azure Storage (served by the Azure CDN) are on a different domain, thus Google indexes the images.
To stop this, Googlebot-Image needs to see this header on the blobs:
X-Robots-Tag: noindex
However, when I try to add this header (as a user-defined header) in CloudBerry Explorer for Azure Blob Storage, the header cannot be added.
So, what’s up with this? Are you preventing me from adding the header? If so, why? If there is no good reason to stop me from adding the header, can you change your policy and allow its use? … or do you have any other ideas?
Issue Analytics
- State:
- Created 8 years ago
- Comments:16 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@GuardRex don’t forget items in the root directory of storage are served from a container called
$rootwhich you’ll have to create.Google Image bot does respect
robots.txthttps://support.google.com/webmasters/answer/35308?hl=en@guardrex i’m also facing the same scenario. I want to add X-Robots-Tag = noindex in the blob storage http header. How did you resolve your issue?