I created a Styled Media Receiver. Hosted the css and images on AWS S3. I started showing up after few hours. Then I changed the images for logo and splash, but, still old images are showing up. I even factory reset the chromecast and connected again, but no respite.
Does anyone has any clue?
If you are using the same name for the updated images, maybe S3 is caching the images or css? Try renaming them and update your styled application settings and see if that does any good. You can also start a chrome debug session and see what images are pointing at to catch any possible issues that way as well.
Related
I am using Laravel 8.0.
Many email providers do not support box-shadow peroperty of CSS. Therefore as a work around, I'm loading images with box-shadow.
This is the image I'm loading from skillshare website and when I use direct link in my blade email template, this image is loaded correctly and that's how it looks.
But then I decided to save this image in my S3 bucket and serve it through CDN, in that case Gmail not showing the box-shadow of the image but rather it is being displayed as black background as below.
I viewed the same email at https://temp-mail.org/, and the imaged loaded correctly here.
My issue is related Gmail and occures when image is loaded from S3 bucket.
When uploading an image in Netlify CMS, I get a preview image, which however disappears right after a refresh. The image I attached shows the source attribute the preview element uses - it looks like the logic here assumes that the image is already deployed to the same domain (which in turn assumes that the site the CMS manages lives on the same domain as the CMS interface itself). Is there a way to change the base URL just for the preview, e.g. to some kind of https://rawgit/...-like URL. I am looking for a setting that affects only the preview widget behavior and nothing else (where the image is saved, what URL path it adds in the post frontmatter etc).
Thanks in advance for any pointers!
I am developing a react app that loads images from a public s3 bucket, this has been working consistently for months. Today I upgraded to google chrome 76 and instead of loading the images it just returns a blank.
The same effect was seen on a number of machines.
Interestingly the request for the image returns 200 but there's no image shown. If I visit the S3 url link manually the image is visible.
I was wondering if it could have anything to do with this forum post and new security measures introduced in the new version of chrome?
Here's a snippet of the content security policy we have for image requests
<meta
http-equiv="Content-Security-Policy"
content="img-src * 'self' blob: data:;"
/>
Is there anything I can do to get these images loading again?
I have got to the root of this and it seems like this was a CORB issue. Which must have been updated slightly in the new v76 release.
What was happening is that, when we were uploading the images to S3, we weren't explicitly setting the Content-Type header in the upload request. S3 then was incorrectly deriving the Content-Type as application/x-www-form-urlencoded. So when we tried to GET the images and load them into an img tag, Chrome saw this as invalid (understandably) and then blocked them.
Interestingly, the images have been loading in with the wrong content type fine up until now and I wasn't shown any CORB warnings until I started uploading new images.
Useful article on CORB for developers
Stack Overflow Article that helped:
How to change content type of Amazon S3 objects
Hope this helps!
I just added an OpenGraph image to a site I'm working on and using the FB Debugger the info retrieves the correct image, however when sharing the url I still see default images being displayed (there was no specified OG image before). Is there something I'm missing here? The site uses a custom Python based framework and image is served via gzip from an Amazon EC2 instance, if that would affect the output in any way.
The problem is not with your website.
Facebook takes some time to refresh images inside facebook.com even though you can see the changes on Facebook Debug Tool.
In order to view your new image inside Facebook you can do two things:
Manipulate a little the URL you are trying to share, this way
Facebook will fetch the open graph data again.
Just give it some
time, it will be refreshed after a few hours.
There are three way to change your image you need to clear the
1) Manually clear facebook catch using the https://developers.facebook.com/tools/debug/ facebook tool
2) Add version code end of the url like ?v=1
3) write the GraphAPI code from when you click on the share button it will clear the facebook page cache.
I'm developing a JSF application which has an image upload function. I'd like to display the uploaded image. The uploading works fine but when I delete the uploaded picture and upload a new one, the old one is displayed in the browser. I typed the link of the picture in the browser but I sill get the old one. I use the same file name and I would not like to change it. How could I refresh it. (without Javascript). I'm using Glassfish Server. (Redeplyoing the application I get the new picture but it isn't a solution for an online system ;))
Thank you.
Redeplyoing the application I get the new picture
Don't store it in the deploy folder by getRealPath() and consorts. Store it outside the deploy folder.
See also:
Uploaded image only available after refreshing the page