Twitter @sam_et_max failed with error 302

[Glandos]

Error message: The requested resource cannot be found! Please make sure your input parameters are correct! cUrl error: Maximum (20) redirects followed (47) PHP error:
Query string: action=display&bridge=Twitter&context=By+username&u=sam_et_max&format=Atom
Version: git.master.eb942bc

It just happens after an upgrade.

[ShaneZampire]

My website Twitter hashtag reader been working for months perfect. It just started the "Bridge returned error 302! (18103)" too. Twitter must have changed something.

[martywd]

I've been intermittently seeing the same errors the OP posted above on twitter accounts I've subscribed to on my rss-bridge.

I guess @triatic has figured out the issue as well as a fix which is awaiting merge?
.

[teromene]

It should be fixed now !

[JonTabor]

I started seeing this as well, so I pulled the latest version from git, but I'm still getting the error. Did I pull too soon (I pulled about 20 minutes ago)?

EDIT: Alright, I think I figured this out. Had to tweak my php.ini and set allow_url_fopen=On. I'm on OpenBSD 6.5 using httpd, in case anyone else runs into this issue.

[dedioste]

Same experience for me; had to turn allow_url_fopen=On in php.ini
this is quite the change fro the norm, I think it needs to be highlighted

[triatic]

The PHP default for allow_url_fopen is "1" (on). This shouldn't be an issue for most installations.

[JonTabor]

OpenBSD, at least, comes with allow_url_fopen set to off by default; part of it's "secure by default" ethos. Not sure about other distributions.

[triatic]

Fair enough. My point really being that allow_url_fopen is not an extraordinary setting and FB2Bridge relies on it too (I copied most of the getCookie code from there).

It would be possible to get the cookie via curl but if someone does that I request the existing behaviour is maintained on this condition:

if(php_sapi_name() === 'cli' && empty(ini_get('curl.cainfo'))) {

[triatic]

@JonTabor can you check PR #1245 to see if it works ok now with allow_url_fopen disabled?

[JonTabor]

@JonTabor can you check PR #1245 to see if it works ok now with allow_url_fopen disabled?

Yep, that seems to work perfectly. Thank you!

[dedioste]

@JonTabor can you check PR #1245 to see if it works ok now with allow_url_fopen disabled?

confirmed working for me too with allow_url_fopen set to Off