-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent failures to fetch price #48
Comments
I have been seeing the same issues on and off for the past week or so. It cleared up today only for about an hour and now I am getting an error when trying to fetch prices once again. |
I'm getting consistent errors as far as I can tell. What do you all see for the |
I wish I knew how to fix this - such a great program - too bad it's broke. |
FWIW the premium version of "TripIt" has this functionality... It has saved
me a lot of money a few times rebooking SWA flights
…On Tue, May 7, 2019, 2:22 PM tjs198 ***@***.***> wrote:
I wish I knew how to fix this - such a great program - too bad it's broke.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJXKKIPMJM7WDC5MWKKXK73PUHJH5ANCNFSM4HGQFLTA>
.
|
Does TripIt work for trips booked with points? Or just dollars? |
I've been experiencing relatively consistent failures to fetch prices, even when routing through a proxy hosted on DigitalOcean. It seems like most attempts to fetch prices result in an error page. I suspect Southwest has changed something in regards to detecting headless browsers, as I'm seeing similar results when trying to view prices (either directly via URL or via manipulating inputs and clicking "Search") via a selenium chromedriver used locally. I'm not sure what the best path forward is here; I'll spend some time over the next few weeks trying to see if there's a workaround, but if the site is detecting headless browsers, it may be the end of the road for this project.
The text was updated successfully, but these errors were encountered: