I saw some recent threads regarding GOG being unavailable to some users and it was found to be due to their browsers directing them to the https version of the site that had been removed.

Now, I never had this issue as my browser was always going to the standard http site. However, this evening I've noticed that as soon as I click on My Account (even to use the Forum Replies option) it goes to a https site. Then any link from the Forum Replies page to navigate the GOG community is a https site but the links on the top bar to return to the site return it to standard http again. I don't appear to be experiencing any issues, however.

So, can anyone else confirm that this is how it is working now and that GOG has both http and https sites once more?

EDIT: Looks like this did post after all, even though the window was stalled.

EDIT: Now, oddly enough, when using the community after visiting Forum Replies (so that the community is in the https site) I get odd issues where the post window just sits there doing nothing. Also, if logging out and logging in whilst that window in https remains open seems to cause issues with accessing the Forum Replies and Messages pages. This was solved by logging out, closing the browser window and opening a new one at the http site to log back in.

The problem was with there having been a https front page at one point, and they removed it. Browsers like Firefox remembered that there's a https version and thought "well, I'd better use the safe one", and tried to access a site that doesn't exist, but weren't smart enough to then automatically try the http one.

The safety needing areas have always been https, as far as I know. You don't really need it for the front page.

You can emulate this by clicking this link https://www.gog.com/

/edit: should probably mention that I'm not all that knowledgeable about this stuff, it's just what I think I heard. if you want a secure front page for some reason, try https://secure.gog.com for all that security

There is still an all-https version of the site, it's just that you need to access it through https://secure.gog.com rather than the URL you linked, and that a lot of the links still point back to the non-https version anyway, so if you want to use https on the whole site you'd have to do quite a bit of legwork.

I found two bits of the puzzle (one required, one not, but useful) and built a necessary third, to prod my browser into secure mode.

Try something for me then. Using the normal http://www.gog.com site, click on the Forum Replies option on the My Account dropdown. Does it direct you to a https://secure.gog.com site? Then click on one of your posts and see if it is still at the https site.

I just thought it odd that I was bouncing between http and https when only using the community, and found that it was the My Account -> Forum Replies option that was doing it.

There are 3 solutions

1: Miaghstir's HTTPS Everywhere ruleset
2: Delete everything in your browser history that starts with https://www.gog.com
3: GOG could configure their server to give a 301 response to every https://www.gog.com request

No, I load up GOG with http://www.gog.com. But the My Account -> Forum Replies redirects to the community via https://secure.gog.com instead. No idea why as the community wouldn't need that, and it only does this if you visit the Forum Replies page via the My Account button.

And this is the only true solution of those presented above. They could, of course, do the actual sensible thing and not use different domains for http and https requests (I'm sure there's proxies that can transparently redirect the requests to another box if that's the intent).

Interesting, today the My Account dropdown now only uses the https://secure.gog.com/ for My Games and Messages, the Forum Replies is now the standard http address. Did GOG fix this or is something weird going on?

This works for me. Thanks. I've included my ruleset below if anyone wants to copy it. Let me know if anyone finds any bugs or can suggest any improvements.

http://pastebin.com/3nZUUZF4

target host="www.google.com" should probably be changed to www.gog.com

Also, here is the post with my ruleset that I referred to (it takes into account a couple more combinations compared to yours, I believe), should've probably linked that one to begin with, saving you the effort.

Thanks. Not sure how that google line got in there. Must have been a copy/paste error.

Well, there was one user who claims to have discovered GOG by mistyping Google, but yes, mistyping the other way around seems a little less probable.