Image Blocked by Security Plugin on Twitter / X

[Ian]

When sharing a post on Facebook and Twitter / X – the images appear in Facebook but are not appearing on the Twitter / X posts, IE – https://walkingfootball.com/united-vs-cancer-24-hour-walking-football-challenge-in-support-of-prostate-cancer/

GROK reported

Both the twitter:image URL you specified and the larger scaled version referenced in schema/Open Graph
(https://...-scaled.jpg) return HTTP 400 Bad Request errors when accessed directly.The error page explicitly mentions: “walkingfootball.com 400 Bad Request Error. […] Thank you. BPS Pro Plugin 400 Error Page”

Can you let me know where I need to whitelist Twitter x and allow it access to the images please

Many thanks

[AITpro Admin]

BPS is not blocking the X shared post. Your web host server is not able to process the content/code of the X shared post. The error message is indicating the problem is with your image URL in the X post. So what I would recommend is creating a simple URL that only contains a link to your website page or post instead of trying to include a link to an image or a page or post on your website. Or you can instead create a post on X with your image and then link it to your image on your website.

The HTTP 400 Bad Request client error response status code indicates that the server would not process the request due to something the server considered to be a client error. The reason for a 400 response is typically due to malformed request syntax, invalid request message framing, or deceptive request routing.

[Ian]

Hi,

The server techs said they are not blocking twitter.

I created as basic a post as possible – https://walkingfootball.com/test/

Shows up fine on facebook – https://www.facebook.com/WalkingFootballdotcom/posts/pfbid02TkHpGR4Zt6d3n1UNFY77AfEpEtqeL82U9TjkTqJ2UHgsVFtajCxtU1s5UZv1FYewl

But on twitter just the blank holding card image again – https://x.com/WalkingFootball/status/2028839969972723911

Can you confirm bulletproof is definitely still not the issue?

Many thanks

[AITpro Admin]

A 400 error does not mean something is being blocked. It means your code has a mistake that cannot be processed by your server or your server is simply refusing to process the Request because the Request is malformed (gibberish) or seen as incorrect. A 403 error means something was blocked. So yeah neither BPS or your host server is blocking the Request.

I tested clicking your test X post and it is working correctly and sends me to your website test page. Looking at the Source Code of the X post, X is using a link shortener. This is the shortened URL to your website page > https://t.co/6C9nVrgbs4. If you are still seeing a 400 Bad Request error then clear your Browser cache.

[Ian]

Hi,

Yes when I click the link on twitter I get to my website fine, the issue is twitter itself is not showing the image from my website like facebook does.

We are trying to find out what is blocking the image from being displayed on the twitter platform

Hope that makes sense

[AITpro Admin]

Then what is causing the problem is the HTML code that you are using to link the image. Most likely the HTML code contains something that is being rejected by your host server as invalid. Below is basic and standard HTML code to link an image and most importantly it must contains the full URL to the image. If an img src url does not contain the full URL to the image then X will not be able to generate a shortened URL.

Example: <img src=”not-a-full-image-url.jpg” alt=”Example”>

<a href=”https://www.example-external-link.com&#8221; target=”_blank”>
<img src=”https://www.example-image-source.com&#8221; alt=”Description of the image”>
</a>

[AITpro Admin]

Looking at this X help information, you may not be able to hotlink images from your website.

X (formerly Twitter) generally does not encourage or support direct hotlinking of images hosted on its servers (pbs.twimg.com) to external websites, such as embedding them in blog posts or as site elements. While the images may load temporarily, they often fail or get blocked because X wants to control image delivery and protect bandwidth.

Sharing Content: To share images, it is best to use X’s provided embed tools, which generate proper HTML, rather than direct links to the media URL

[Author]

Posts