Facebook went into infinite reload loop, cookies are enabled

Post by **moonbat** » 2019-10-05, 14:09

I was going through about:config and I may have goofed up something

Result is that Facebook goes into an infinite loop of trying to reload, but won't trigger the usual 'this site is reloading many times' warning (because cookies are enabled for it).
I'm not sure what I messed with so I've attached the troubleshooting info - can someone figure out?

Post by **Moonchild** » 2019-10-05, 14:57

Try resetting your http referrer preferences to defaults.

Post by **moonbat** » 2019-10-05, 15:22

I reset all the network.http.referer settings and network.http.sendRefererHeader, still the same problem. Have disabled uBO and nMatrix on Facebook as well.

coffeebreak · Post by **coffeebreak** » 2019-10-05, 15:33

moonbat wrote: ↑
2019-10-05, 14:09
I was going through about:config and I may have goofed up something

Result is that Facebook goes into an infinite loop of trying to reload [...]
I've attached the troubleshooting info - can someone figure out?

Did you go through troubleshooting steps to determine if that's in fact the case?
(as opposed, eg, to the problem being caused by something Facebook is doing)

1. Safe mode to rule extensions out...?
2. If extension/extension's settings are ruled out, trying Facebook with a vanilla profile...?

Post by **moonbat** » 2019-10-06, 08:57

Works in vanilla profile, I've gone through the drill. Pretty sure it isn't the extensions because I haven't added or updated any, just the settings.

coffeebreak · Post by **coffeebreak** » 2019-10-06, 09:21

moonbat wrote: ↑
2019-10-06, 08:57
Pretty sure it isn't the extensions because I haven't added or updated any

That doesn't guarantee that Facebook didn't change something
(something that affects how an extension interacts with the site).

Did you test with all extensions disabled or not?
Because if not, testing with a vanilla profile doesn't narrow down whether a problem is related to extensions or browser settings.

Post by **moonbat** » 2019-10-06, 09:22

coffeebreak wrote: ↑
2019-10-06, 09:21
Did you test with all extensions disabled or not?
Because if not, testing with a vanilla profile doesn't narrow down whether a problem is related to extensions or browser settings.

Do you mean the usual safe mode, or actually disabling each and every one of them?

coffeebreak · Post by **coffeebreak** » 2019-10-06, 09:40

Think systematically.
Safe mode disables more than extensions (read linked article above).

Returning from safe mode is somewhat faster than disabling/and then reenabling all extensions.
But if the problem is gone in safe mode, and you want to rule out the non-extension things that safe mode disables, next try just disabling extensions.

Post by **letmeindude** » 2019-10-06, 10:03

@Moonchild

This could be easily avoided if there is something like a simple log file. For example:

25.09.2019. dom.disable_window_flip changed (nondefault)
27.09.2019. NoScript 5.1.9 installed
01.10.2019. network.cookie.cookieBehavior changed (nondefault)
04.10.2019. network.http.altsvc.oe changed (nondefault)
05.10.2019. network.http.referer.spoofSource changed (nondefault)

It would save user time, support time, etc.

Post by **Moonchild** » 2019-10-06, 10:34

letmeindude wrote: ↑
2019-10-06, 10:03
@Moonchild

This could be easily avoided if there is something like a simple log file. For example:

25.09.2019. dom.disable_window_flip changed (nondefault)
27.09.2019. NoScript 5.1.9 installed
01.10.2019. network.cookie.cookieBehavior changed (nondefault)
04.10.2019. network.http.altsvc.oe changed (nondefault)
05.10.2019. network.http.referer.spoofSource changed (nondefault)

It would save user time, support time, etc.

And most people wouldn't want to have a record of everything done in the browser stored. So it'd have to be disabled by default, meaning it would not be used by the people who would need it because they don't heed the warning on about:config and get roasted by dragons.

Post by **letmeindude** » 2019-10-06, 10:46

Whaaaaaaaaaaat ???

Moonbat and everyone else who wants support need to give you "Troubleshooting information" which means all installed extensions and all modified preferences (and more), but this log which could have only last ten days of installed extensions and changed preferences is a privacy problem? Sorry, but that doesn't make any sense.

EDIT: All I am saying, moonbat and everyone else who is "playing" with about:config would solve this problem without even asking for support, if they had this log file. IMO this log file is a must for me and everyone else who are using about:config.

Post by **Moonchild** » 2019-10-06, 10:56

Please keep your moral outrage in check.

A default-enabled logging facility would impact every user of the browser, not just the ones needing support.
Even for the ones needing support, asking them to post the log instead for troubleshooting would be a much worse thing than posting the current state, and to reflect this right back at you: it would also have a log of all installed extensions in it (and those ever installed and now uninstalled). Time-limiting this log would also not work because a preference change a long time ago can impact something much more recent, and if that's dropped form the log it would make troubleshooting harder, not easier.

So you see, I did think about several aspects of this already, and it's really not a good idea.

Post by **Moonchild** » 2019-10-06, 10:58

letmeindude wrote: ↑
2019-10-06, 10:46
EDIT: All I am saying, moonbat and everyone else who is "playing" with about:config would solve this problem without even asking for support, if they had this log file. IMO this log file is a must for me and everyone else who are using about:config.

Then I have a suggestion: make an extension that does this, that people who find it "a must" can install.

Post by **moonbat** » 2019-10-06, 11:01

Found out the problem. Wasn't about:config, but overzealous parameter blocking using Pure URL. Safe mode showed no problems, so I moved onto disabling extensions, I started with the likely ones that modify permissions/pages and after disabling Cookie Masters, this was the next one.

Post by **letmeindude** » 2019-10-06, 11:08

moonbat wrote: ↑
2019-10-06, 11:01
Found out the problem. Wasn't about:config, but overzealous parameter blocking using Pure URL.

And that parameter was default one or added by you? I am asking for other "Pure Url for Pale Moon" users.

Post by **moonbat** » 2019-10-06, 11:13

Added by me obviously, else it would be broken everywhere.

Pale Moon forum

Facebook went into infinite reload loop, cookies are enabled

Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled

Re: Facebook went into infinite reload loop, cookies are enabled