Stupid cookie requirements (for future references)

[kosukesando]

I'm not sure where to write this, but thought it might help some poor folk in the future so they don't have to suffer.

I was trying to setup a CSSSelectorBridge for "The Australian", but it kept on failing for some reason. I looked at the error page on RSS Bridge and the website title read "NoCookie | blah blah" so I thought "huh, I guess I need cookies?".

Then I went and enabled CSSSelectorComplexBridge (which was a little confusing for me as a docker compose user, I had to figure out I needed to create a config.ini.php file in the :/config dir which in hindsight is obvious), fetched all the request cookies with debug console, and entered that into the cookie input (note: key=value needs to be semicolon separated. I guess pretty standard knowledge for frontend folks?). Voila, now it's working.

Finally I wanted to drill down which of the cookies are necessary to bypass bot blocking.

Turns out all I need is "n_regis=123456789;"

What a joke.
Well, I hope it helps someone.

[dvikan]

Thanks. Yes it's confusing. How can we make it less confusing? The current README has docker instructions, take a look?