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
The initial flight query always fails with a message saying "Sorry, we found some errors..." If I print out the fullUrl and paste it into a browser, the url does not actually have any errors, it works fine. The problem only happens when running from selenium. I've tried with both Firefox and Chrome with the same result. If I hold the selenium controlled browser open and paste in the fullUrl, I still get the "Sorry, we found some errors..."
I suspect southwest is detecting that this is automated and then refuses to give search results.
The text was updated successfully, but these errors were encountered:
Hello:
Sorry about the delay writing back – I had meant to when the message was received, but then it slipped my mind.
Anyway – I haven’t run Swatcher in quite a while – it was properly scraping prices, but then Southwest made a change to their firewall/infrastructure that must detect whether flight searches are coming from a typical browser session or from directly doing a REST query, and if it detects you coming directly, it only allows one or two queries over some period of time (never looked deep enough to figure out what the metric was) until it blocks the request IP. Games could always be played to route each request through an anonymizer, but never dug into it.
-john-
From: spehrson ***@***.***>
Sent: Friday, November 11, 2022 12:16 PM
To: techtricity/swatcher ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [techtricity/swatcher] May no longer work (Issue #1)
The initial flight query always fails with a message saying "Sorry, we found some errors..." If I print out the fullUrl and paste it into a browser, the url does not actually have any errors, it works fine. The problem only happens when running from selenium. I've tried with both Firefox and Chrome with the same result. If I hold the selenium controlled browser open and paste in the fullUrl, I still get the "Sorry, we found some errors..."
I suspect southwest is detecting that this is automated and then refuses to give search results.
—
Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB4RNGC44N4Y2HRSPOYESWDWH2EN3ANCNFSM6AAAAAAR52M6SI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
The initial flight query always fails with a message saying "Sorry, we found some errors..." If I print out the
fullUrl
and paste it into a browser, the url does not actually have any errors, it works fine. The problem only happens when running from selenium. I've tried with both Firefox and Chrome with the same result. If I hold the selenium controlled browser open and paste in the fullUrl, I still get the "Sorry, we found some errors..."I suspect southwest is detecting that this is automated and then refuses to give search results.
The text was updated successfully, but these errors were encountered: