-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pull search information with POST and json data #9
Comments
Tested with |
Parsing session storage worked. Each train is stored in the following path:
This not only makes parsing a page faster as we just need session storage, but it also reveals a lot of hidden data such as fare types and train information for multiple segments, seating accommodations, etc. Would need a deep dive. |
Useful keys from session storage. |
After closer examination:
|
JSON data only |
Included in a (future) commit are a headers file and resulting search results json data (stored in session storage). At the very least, the data could be parsed quicker than checking each browser element could.
The text was updated successfully, but these errors were encountered: