Visiting  and then navigating to other sites of the Stack&nbsp;Exchange network through the top menu bar, then the other sites are called without https.  The links in the menu should be fixed.
44470
When I'm on, for example, the secure SO site, and then open the "StackExchange" drop-down, links to other SE sites include their "https" equivalent as well, which is expected. (If I'm on the the regular http site, then the links are all http.)    But links to questions via the "Inbox" and "Achievements" drop-downs lead back to the insecure, http equivalent, even when I'm on a secure page.      Can those links be generated in such a way that we're kept on the secure version of the site?
81681
I have encountered a problem when trying to introduce new people to the SE network: they can't remember Stack Exchange.  So, for example, I might tell a non-tech user: "You should ask your question on this cooking website, it's called cooking.stackexchange.com." They remember the cooking part very easily (or the diy, or gaming, etc..), but they tend to forget the stackexchange part.  So what I propose is that we buy domains for all Area 51 site proposals that end in *.se. So, for example, cooking.stackexchange.com would be magically transformed into cooking.se.  I understand that it isn't a .com but it could be forwarded to *.stackexchange.com    Most (if not all) of the domains should be available since this is a . I'm not 100% sure if non-Swedish compaines/people can register these domains .  This is not the same as  since it proposes we use *.se.com. Also the accepted answer for  was basically that "all sites will get their own .com once they leave beta," which we now know isn't the plan.
9493
Stack Overflow has HTTPS in some places! However, this breaks most existing image links. Could those be made protocol-relative, or react to the requesting protocol, or just always use HTTPS?  The same applies to .sponsor-tag-img.
102693
When I click on the drop down menu in , it does not show the site browsing menu. Instead, it loads the homepage. But it is working fine on other Stack Exchange sites.
122218
Clicking on  doesn't connect me with the meta S.Ex.SE site.  EDIT: For some entry points, . Observation courtesy Gilles.  I consider it a pity that the devs have not paid attention to this issue nor have indicated that they noted the problem. While HTTPS is not yet official on this network, I refrain from using unencrypted connections. I can't participate in metas, oh well.  EDIT #2 (2015-11-07) - with the switch to CloudFlare SSL the problem looks finally resolved.  EDIT #3 (2015-11-17) - still getting 403 Forbidden from CloudFlare. D'rats!..  EDIT #4 (2016-01-11) - We're still there. It's 2016 already... Starting a bounty.
75826
Anyone know how to disable certain SSL versions and only enable others in IIS 7.5?
60639
I recently tried to visit a person's profile from chat room.  I clicked the link to his profile(points to area51) and the link is dead.    The link points to discuss.area51.stackexchange.com and the link should be area51.meta.stackexchange.com (as pointed by Shadow Wizard in Tavern on meta).  This link points to an HTTPS error page       I am able to reproduce this issue only for users with main profile in area51.   And I think someone missed it in the recent meta url changes from meta.x.se to x.meta.se
11642
Someone just edited a link in one of my answers to point to a 'better reference'.    I've no problem with links being changed in general, but this smells like part of a concerted attempt to redirect traffic.   Is this kind of activity acceptable on SO?
92637
The Community bot already ran through posts to convert internal http:// links to https://, which is great, but it needs to be run one more time: this time, it needs to convert links of this format:  https://meta.example.stackexchange.com/   to this format:  https://example.meta.stackexchange.com/   Our old meta pages on RPG Stack Exchange contain lots of internal meta references which still follow the old (first) domain protocol.  This link points to rpg.meta and is fine:   However this link points to meta.rpg and contains a privacy error in Chrome because meta.rpg.stackexchange.com doesn't actually have a certificate:         As you can see this means people trying to visit meta links posted before a few months ago are left with no obvious option of how to actually reach the intended destination. They'd also be confused why an obviously Stack Exchange URL is breaking.  Please run that Community edit script another time!  Reported locally on our RPG.SE meta as well here:
19534
When posting an HTTPS url like https://stackoverflow.com/..., it does not onebox in chat. For example:
34445
As figured out in  localized SE sites must not be displayed in the HNQ's. But  actually is.        Has to be fixed I guess?
74156
The search results on  are blocked because of:     [blocked] The page at  ran   insecure content from .   I am using Chrome.
55027
I had something set up wacky in our DNS setup which is now resolved. The remaining problem is that chrome has cached the incorrect setup. Specifically, when using Chrome http://example.com is now redirecting to https://example.com (naked domain), which is not valid/supported.  http://example.com SHOULD redirect to http://www.example.com and then force https://www.example.com. But on a handful of browsers (including mine) this doesn't happen because of some funky Chrome caching. I tried going to “Privacy -&gt; Clear Cache” but it had no effect.
112771
One thing that seems to be missing in the Top&nbsp;Bar is a link to the Stack&nbsp;Exchange portal. It only displays under the "Current&nbsp;Community" section when you are in the community, but it disappears as soon as you go to another one.  Would it be possible to add a link that would always be there no matter which community you are currently on?
122136
I've called GoDaddy a few different times and they said that it looks like it is a problem with my HTML file.  Except, my HTML file is the basic outline of a webpage, nothing fancy at all.    Chrome still says that the webpage is, "Not Secure" with the big red x over it.    I'm not sure what to do to fix it, I don't have any personal information on the site nor am I collecting any information from visitors (it's sort of an information site).  I shouldn't need an SSL certificate because I am not hosting anything privately.
44335
Following a global preference for , as of now, the preferences for enabling keyboard shortcuts and disabling the fixed topbar are network-wide* as well.  If you had either checked off on any site in the network, that setting has been preserved and applied to the whole network for your account already. Future changes will also apply to all* Q&amp;A sites.  Find them in their usual spot as previously on the  pages.    * With the exception of , which will support the fixed topbar after the .
34124
On my web server I have a bunch of websites defined using VirtualHosts. Currently if I request a website from my webserver that is not defined as a virtual host, I will get back the first virtual host in the list.  I would like to make it so that any requests that ask for a website not defined in a virtual host will just close the connection, both for HTTP and HTTPS. I imagine this will involve creating default and default-ssl virtual hosts but I am unsure what exactly to put in them.