Lately I get constant problems on GOG with Firefox trying to load some pages and failing. See an attachment for how the loading process looks in the Firefox network monitor.

And it happens on quite a number of game pages. Any idea what's going on?

This may help:

http://kb.mozillazine.org/The_page_isn%27t_redirecting_properly

I did clear cookies for GOG already. So it must be a problem on GOG's side. I suspect it's some mess caused by GOG's inconsistent support for HTTPS.

It's pretty annoying since I can't even check out my purchase.

Try with another browser like Opera (i'm now from it, zero problems).

I was using Mozilla on Linux and got that problem in other sites too, probably is a bug.

It worked for me in the end, this problem happens intermittently. But I'm not sure if it's a bug in Firefox and not some issue with the site.

try a different firefox derivative ?
like palemoon

or seamonkey ( tis what i use )

Do you have a security plug in or software that might try to stop or redirect redirection?

I tested it with add-ons disabled, and it still happened. I blamed it on HTTPSeverywhere add-on, but this happened even without it. Strange part - it happens only periodically and not all the time that's why I suspect it's server problem. I'm using another mail client (actually switched from Thunderbird to KMail some time ago), so Seamonkey would be an overkill. I've never heard of Palemoon before. Why did they remove support for WebRTC from it? That's kind of a no go really.

I've only seen this with HTTPSeverywhere enable. The game pages usually/mostly fail with that error. The rule I'm using tries to force https, but doesn't attempt to rewrite any cookies (if that would even help). Disabling it & reloading the page has worked all the times I've tried it. In fact it usually works over https after I've allowed the page to redirect to http first.

May be cookies get messed up because of the add-on, and that has an effect even when it's disabled.

My rule looks like this

<ruleset name="GOG">
<target host="www.gog.com"/>
<target host="gog.com"/>

<rule from="^https://www.gog.com/" />
</ruleset>

Also, please vote here for GOG to fix this HTTPS mess: https://www.gog.com/wishlist/site/https_browsing_of_the_whole_site

Corresponding thread: https://www.gog.com/forum/general/dear_gog_please_fix_your_https_pages_linking

Mines the same except for the trailing slash & the target host order is swapped.

Voted a while ago. Would like to see it break 1000 votes.

I saw this start happening when the new site design went live. If you open the details view in the Firefox network monitor, you can see what happens:

Fx requests https://www.gog.com/FOO
Server responds with a redirect to http://www.gog.com/FOO
In the broken case, Fx (usually under the influence of an extension) rewrites that back to https://www.gog.com/FOO
If you hit a server which sends a redirect to http://www.gog.com/FOO, then Fx will again rewrite it to https://www.gog.com/FOO and the cycle continues until either you hit a server which is willing to serve the content over https or Fx decides the server is broken. In the latter case, you get the error message shown in the opening screenshot. The bad result is intermittent because some GOG servers will serve the content over https, but others always redirect you to insecure http.

I see the problem when using NoScript to force www.gog.com to HTTPS (https://noscript.net ; Options -> Advanced -> HTTPS -> "Force the following sites to use secure (HTTPS) connections"). When I disable that, but allow HTTPS Everywhere to rewrite links, the rewriter will eventually give up and drop to plain http if the servers keep issuing bad redirects. NoScript's HTTPS logic is simpler. It always rewrites matching sites, so you either get a working server or you get the Firefox message about a redirect loop.

Thanks for clarifying. The strange part is that it happened even when I disabled HTTPSeverywhere.

I wish GOG would fix this redirects mess and fix referencing insecure pages from secure ones within their own site. Can you please submit a ticket to them? I already did a while ago, but apparently they didn't do anything about it.

I tried going to the Unreal 2 page using Firefox 33.1.1 now and it worked fine. I don't remember having this problem. (But I don't usually browse games, I'm usually just on the forum.)