Skip to main content
Meta Stack Exchange

Return to Answer

edited body
Source Link
Mithical
Mithical
  • 84.5k
  • 28
  • 145
  • 315

I agree with you that SE should be using something protocol-agnostic. As per the answer given by AnnaAdam Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the commentcomments:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically, it's a work-in-progess and that's a good news.

I agree with you that SE should be using something protocol-agnostic. As per the answer given by Anna Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comment:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically it's a work-in-progess and that's a good news.

I agree with you that SE should be using something protocol-agnostic. As per the answer given by Adam Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comments:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically, it's a work-in-progess and that's good news.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

I agree with you that SE should be using something protocol-agnostic. As per the answeranswer given by Anna Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comment:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically it's a work-in-progess and that's a good news.

I agree with you that SE should be using something protocol-agnostic. As per the answer given by Anna Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comment:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically it's a work-in-progess and that's a good news.

I agree with you that SE should be using something protocol-agnostic. As per the answer given by Anna Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comment:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically it's a work-in-progess and that's a good news.

Source Link
HackerKarma
HackerKarma
  • 6.2k
  • 2
  • 20
  • 44

I agree with you that SE should be using something protocol-agnostic. As per the answer given by Anna Lear: (copied only relevant part)

Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.

We should use protocol-relative URLs more, I agree,

Also from the comment:

All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :)

So, basically it's a work-in-progess and that's a good news.