All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Menzel <paulepanter@users.sourceforge.net>,
	intel-gfx@lists.freedesktop.org, "Vivi,
	Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: 01.org: HTTPS: Please fix mixed content loading
Date: Mon, 25 May 2015 12:47:07 +0300	[thread overview]
Message-ID: <87a8wtj8f8.fsf@intel.com> (raw)
In-Reply-To: <1432391276.5111.23.camel@users.sourceforge.net>

On Sat, 23 May 2015, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> Dear Intel folks,
>
>
> accessing the resources at 01.org over HTTPS, some have mixed content
> loading issues. For example [1] loads an image from Gravatar – for
> whatever reason – over HTTP.
>
> Google Chromium reports for example the following.
>
>         Mixed Content: The page at 'https://01.org/linuxgraphics/documentation/how-report-bugs' was loaded over HTTPS, but requested an insecure image 'http://www.gravatar.com/avatar/672c5e6b44ca5810141d82f730aad074.jpg?d=mm&s=50&r=G'. This content should also be served over HTTPS.
>
>
> Thanks,
>
> Paul
>
>
> [1] https://01.org/linuxgraphics/documentation/how-report-bugs


Thanks for the report, Paul.

Rodrigo, please pass this on to whoever it is that maintains the site.

Thanks,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-05-25  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23 14:27 01.org: HTTPS: Please fix mixed content loading Paul Menzel
2015-05-25  9:47 ` Jani Nikula [this message]
2015-05-26 18:05   ` Vivi, Rodrigo
2015-05-29 21:10     ` Rodrigo Vivi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8wtj8f8.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulepanter@users.sourceforge.net \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.