Closed dolohow closed 1 year ago
Hi,
I'd rather not try to actively circumvent any of these kinds of checks or protections as part of this library.
My ultimate intention was to allow users to make use of APIs that were readily accessible without requiring any kind of spoofing on our part.
Clearly, they've decided they don't want people directly accessing the availablity API, and it's not my intention to try circumvent this decision. They likely have their reasons, and I respect that.
With this in mind, I will likely, regrettably, remove the availablity API endpoints from the library in the next major release.
So I've been using this on daily basis
Recently, they introduced check for
User-Agent
header. It was an easy fix, obviously.However, today they rolled an update that requires running JavaScript in order to set cookies. I already have a code that is using
playwright
to fire up headless browser.Would you be willing to accept it? Should I prepare PR?