Skip to main content
footnote
Source Link
Floern
  • 2k
  • 2
  • 18
  • 21

This is caused by the switch to HTTPS.

Stack Overflow changed to HTTPS on May 22, and guess what happened. Here are the awarded Announcer badges on Stack Overflow:

announcer badge graph 12017

This has a technical reason. Visitors coming from within the Stack Exchange network didn't count towards the badge as they were filtered out using the HTTP Referer header. The problem is, HTTPS disallows cross-domain Referers1, thus visitors from within the network, even from child metas, can no longer be distinguished from outside visitors.

1: not entirely true, see comments for details.

This is caused by the switch to HTTPS.

Stack Overflow changed to HTTPS on May 22, and guess what happened. Here are the awarded Announcer badges on Stack Overflow:

announcer badge graph 12017

This has a technical reason. Visitors coming from within the Stack Exchange network didn't count towards the badge as they were filtered out using the HTTP Referer header. The problem is, HTTPS disallows cross-domain Referers, thus visitors from within the network, even from child metas, can no longer be distinguished from outside visitors.

This is caused by the switch to HTTPS.

Stack Overflow changed to HTTPS on May 22, and guess what happened. Here are the awarded Announcer badges on Stack Overflow:

announcer badge graph 12017

This has a technical reason. Visitors coming from within the Stack Exchange network didn't count towards the badge as they were filtered out using the HTTP Referer header. The problem is, HTTPS disallows cross-domain Referers1, thus visitors from within the network, even from child metas, can no longer be distinguished from outside visitors.

1: not entirely true, see comments for details.

Bounty Ended with 50 reputation awarded by Shadow Wizard
Source Link
Floern
  • 2k
  • 2
  • 18
  • 21

This is caused by the switch to HTTPS.

Stack Overflow changed to HTTPS on May 22, and guess what happened. Here are the awarded Announcer badges on Stack Overflow:

announcer badge graph 12017

This has a technical reason. Visitors coming from within the Stack Exchange network didn't count towards the badge as they were filtered out using the HTTP Referer header. The problem is, HTTPS disallows cross-domain Referers, thus visitors from within the network, even from child metas, can no longer be distinguished from outside visitors.