Same problem.
I set meta tag like this,
<meta name="twitter:player" content="https://sample.com/#/contents/test">
I got an error…
Error: Not Found The requested URL /%23/contents/test was not found on this server.
This is an 8 year old thread, so I suspect this is something different.
Where are you getting that error from?
Do you have a resource that the cards crawler can fetch at the URL you have specified?
1 Like
Hi Andy!
My website contains # in the URL because I’m using Nuxt static hosting.
I have configured nuxt.config.js as follows
export default {
head: {
meta: [
{ hid: 'og:title', property: 'og:title', content: 'Sample' },
{ hid: 'twitter:card', name: 'twitter:card', content: 'player' },
{ hid: 'twitter:player', name: 'twitter:player', content: 'https://sample.io/#/contents/sample' },
{ hid: 'twitter:player:width', name: 'twitter:player:width', content: '500' },
{ hid: 'twitter:player:height', name: 'twitter:player:height', content: '500' },
]
}
}
Then I checked with Card Validator and was able to display the card, but when I access the content, I got an Error.
Error: Not Found
The requested URL
/%23/contents/sample?autoplay=1&autoplay=true was not found on this server.
The problem is that the URL in twitter:player is encoded.
How do I resolve this?
I’m guessing that you may need to find a way to link to the content without an encoded character in the URL. I’m not aware of any changes planned on the Twitter side.
We will of course be exploring ways to do that, but it seems to me that there are many examples and other examples where we would like to add parameters to the URL.