@MartinSleziak Haha that's an odd question for you to ask here. If you don't know, which user that comes to this chat-room would? =)
@MartinSleziak: Hey I think I have a guess, based on this Meta post, where only one of the links was updated. I think the automated script only fixed links to the main SE sites, and not the meta sites.
About a year ago, several migration scripts were run to change old HTTP network-internal links across the network to HTTPS links. However, it appears that the script didn't modify links that lack the ending /. For example:
303 results for http://stackoverflow.com
194 results for http://superuse...
Update 2017-05-22
stackoverflow.com is now https://. I've written up a lot of what it took to get here in a blog post.
Next up is chat and then https-only cookies. We'll be ramping up HSTS max-age directives as we go. I'll continue to update this post as we deploy new bits.
Update 2017-03-16
...
So, for example, I know that correcting the links in chat is still to come.
> We've redirected all child meta traffic from meta.*.stackexchange.com to *.meta.stackexchange.com, and are now forcing HTTPS. We have also rebaked links inside the network (except comments) to point to the new domains and protocol. We'll get to comments at the end.
> 9. <kbd>done</kbd> (Child metas) Move from meta.*.stackexchange.com to *.meta.stackexchange.com.
If I am reading that post correctly, even if not converted to https, the links are supposed to be changed from meta.math.stackexchange.com to math.meta.stackexchange.com by now.
@MartinSleziak This is the perfect room for it. I was just joking that you (usually) know better (about this kind of stuff) than practically anybody else here. =)
About a year ago, several migration scripts were run to change old HTTP network-internal links across the network to HTTPS links. However, it appears that the script didn't modify links that lack the ending /. For example:
303 results for http://stackoverflow.com
194 results for http://superuse...
Update 2017-05-22
stackoverflow.com is now https://. I've written up a lot of what it took to get here in a blog post.
Next up is chat and then https-only cookies. We'll be ramping up HSTS max-age directives as we go. I'll continue to update this post as we deploy new bits.
Update 2017-03-16
...
