You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google started enforcing EU consent redirects that the hardcoded
SOCS/CONSENT cookies no longer bypass. Replace static cookie approach
with dynamic consent handling: follow redirect chains, detect consent
forms, submit acceptance, and resume the flights request.
Release v1.6.1
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -285,7 +285,7 @@ In human mode, errors go to stderr.
285
285
286
286
1.**Query encoding** -- Flight parameters are protobuf-encoded (hand-rolled encoder, ~130 LOC) and base64-encoded into the `tfs` URL parameter, matching what Google Flights expects.
287
287
288
-
2.**HTTP request** -- Uses [wreq](https://github.com/nickel-org/wreq) (reqwest fork) with Chrome 137 TLS fingerprint emulation to avoid bot detection. Pre-loads GDPR consent cookies to bypass the EU consent wall.
288
+
2.**HTTP request** -- Uses [wreq](https://github.com/nickel-org/wreq) (reqwest fork) with Chrome 137 TLS fingerprint emulation to avoid bot detection. Automatically handles Google's EU consent wall by detecting consent redirects and submitting the acceptance form.
289
289
290
290
3.**HTML parsing** -- Extracts the `<script class="ds:1">` tag, isolates the `data:` JSON payload, parses with serde_json.
291
291
@@ -341,7 +341,7 @@ src/
341
341
├── mcp.rs Built-in MCP server (rmcp, stdio transport)
0 commit comments