You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, certain emails use HTTP to serve their images. We want to--just like Gmail--proxy those images through HTTPS so that we don't trigger a mixed content warning from the user's browser (which gets rid of the HTTPS "lock" symbol):
Parts of this page are not secure (such as the images).
A gray padlock with an orange or yellow triangle indicates that Firefox is not blocking insecure passive content, such as images. By default, Firefox does not block mixed passive content; you will simply see a warning that the page isn't fully secure. Attackers may be able to manipulate parts of the page like displaying misleading or inappropriate content, but they should not be able to steal your personal data from the site.
The text was updated successfully, but these errors were encountered:
Related to #11, #10, #7, and #5 because this will allow us to further
manipulate the raw Gmail API data (e.g. by sanitizing it, proxying
images through HTTPS) and save our own metadata about it (e.g. the
scroll position or archive status).
Right now, certain emails use HTTP to serve their images. We want to--just like Gmail--proxy those images through HTTPS so that we don't trigger a mixed content warning from the user's browser (which gets rid of the HTTPS "lock" symbol):
The text was updated successfully, but these errors were encountered: