I'm using angular.js library "angular-img-http-src" and my current browser is Edge.
I ran into an issue with uploading images.
In the Chrome browser, there is no problem, the image uploads through an internal file server so the URL points to the file's path and the user token is added to the request header.
In Edge browser, the URL converts to an unrecognized path.
Anyone experienced something similar and can advise a solution?
Related
I know that the easiest way to open a resource in Edge is by using the microsoft-edge: protocol handler.
I think this works for html files. For instance, you could run microsoft-edge:http://stackoverflow.com to open Stack Overflow in Edge.
But, what if I want to open a PDF file?
Can I run microsoft-edge:file:///C:/Desktop/sample.pdf ?
Looks like it's not working for me.
Thanks
I could reproduce the problem on my machine, it seems that you want to open a PDF file in Edge browser from another browser. As far as I know, Edge browser URL protocol no longer works for local files, only for http/https.
As a workaround, I suggest you could upload the local pdf file to the internet, such as OneDrive. Then, we could get the shared link and use it with the Edge URL protocol.
Sample code as below:
Link
I am writing codes to share the page of my website into the facebook. I have used meta tags for open graphs. Previously, the images of the pages were stored in the server itself and I used to supply the link to that image in the meta tag as:
<meta
key="og:image"
property="og:image"
content={coverImage} // link to the image
>
While sharing on facebook, everything worked fine. The image was displayed properly along with title and descriptions.
Recently, I have changed the image store to amazon s3 instead of storing it in server. Now, the coverImage has the link of S3. I supply this link in open graph image tag but the facebook is not previewing the image. I clear the cache, scraped the url again, but the facebook shows the warning:
"Provided og:image, https://***.s3.ap-south-1.amazonaws.com/......*.jpg could not be downloaded. This can happen due to several different reasons such as your server using unsupported content-encoding. The crawler accepts deflate and gzip content encodings."
This image is being previewed everywhere else and I have used ContentType :'image/jpeg', ContentEncoding: 'base64',. I am not really sure why this is being blocked in facebook.
I would be very grateful if anyone could help me resolve this thing.
Thanks in advance.
So, I added the S3 base URL to the App Domain section on "Facebook Developer Console" and it started working.
I'm trying to get a fallback image working that behaves differently based on the status code. My images are coming out of SharePoint and in certain (Microsoft) browsers I have to request the images through a Web API so that I can append the proper authentication cookies.
I already have a fallback working that if an image fails it requests the image through the Web API and gets the Base64 representation. The problem is there's no point doing this if the image isn't there. So if it's a 404 I'd like to just display the placeholder, but if it's a 302 I'll get the image a different way.
Checking the error object and all the fallback directives I can find, I can't see a way to find out the error code.
Thanks!
whenever I visit my angularjs based website that loads images (http images on a https server) I get warnings in the console saying that mixed content has been blocked. And those images do not show up
It is not my browser because it happens on other browsers too and on other systems, it is not the server, because another website that does not use angularjs works fine. So I think it is related to angularjs.
I already did this:
$sceDelegateProvider.resourceUrlWhitelist([
'self',
'http://images.RESOURCE.net/*'
]);
but it does not do anything. Moreover I tried loading them over a protocol-less url so //images.RESOURCE.net
This causes them to be loaded over https but then the server identify of the image server could not be validated and it also does not work.
Is there anyone who can determine the actual problem, is it angularjs and can angularjs fix it? It is almost impossible to remove angularjs from the project at the current state.
Thanks
-xCoder
This is not a limitation of Angular. Modern browsers block the loading of mixed (http) content over a secure (https) connection. This can be addressed by adjusting settings in your browser of choice.
Enabling Mixed Content by Browser:
IE: http://wiki.sln.suny.edu/display/SLNKB/Enabling+mixed+content+in+Internet+Explorer
Firefox: http://wiki.sln.suny.edu/display/SLNKB/Enabling+mixed+content+in+Mozilla+Firefox
Chrome: http://wiki.sln.suny.edu/display/SLNKB/Enabling+mixed+content+in+Google+Chrome
I want to call attention to this issue which is almost a month old and hasn't been acknowledged:
https://code.google.com/p/googleappengine/issues/detail?id=9940
I'm wondering if there's any plans to fix or known workarounds - e.g to force the images to be served in jpg format always via some url modification.
Full issue description below
We've had some complaints that in Firefox and Safari images aren't showing up. These images have urls that were returned from the get_serving_url(blob_key, ... function listed here:
https://developers.google.com/appengine/docs/python/images/functions
For example, this image:
http://lh6.ggpht.com/b8DBpggeo8eZ7TMlJiUJFnMUuBXIkDe_5NZaEtpjfNh9_1BMjxReNBIyU9WMhhb96LDuzndsvdqBaiDiIGIJ=s470-c
Was not rendering in Safari - upon closer inspection using the developer console, I could see it was being served with content-type 'webp', even though Safari isn't saying it accepts image/webp in the request 'accepts' header. Attaching a screenshot of the request / response headers of an image served as webp to safari.
Unfortunately the issue is intermittent - the same image when loaded later may be served as a jpg.
Is it possible the image serving infrastructure is improperly sending back webp images even when the accepts header isn't present? Or perhaps there's some caching server along the way that isn't taking the accepts header into account?