.de.db need to target new URL

[georgjaehnig]

.de.db 2/3/4 currently still work, but Bahn.de is migrating to a new interface. There, URLs look like this

https://www.bahn.de/buchung/fahrplan/suche#sts=true&so=BERLIN&zo=HAMBURG&kl=2&r=13:16:KLASSENLOS:1&soid=A%3D1%40O%3DBERLIN%40X%3D13386988%40Y%3D52520501%40U%3D80%40L%3D8096003%40B%3D1%40p%3D1698259482%40&zoid=A%3D1%40O%3DHAMBURG%40X%3D9997434%40Y%3D53557110%40U%3D80%40L%3D8096009%40B%3D1%40p%3D1698259482%40&sot=ST&zot=ST&soei=8096003&zoei=8096009&hd=2023-10-31T15:41:06&hza=D&ar=false&s=true&d=false&hz=%5B%5D&fm=false&bp=false

There, the tricky part are the soid and zoid parameters. Without them, the URL shows only an error. It seems though hard to guess their contents.

IIRC one can do an API call before to get those IDs, but this functionality is not yet part of Trovu (and would be complex to implement).

This issue has already been asked in Reddit but without success.

[georgjaehnig]

Temporary solution in #284: Use mobile.bahn.de

[georgjaehnig]

If it really remains necessary to prefetch data, trovu could be extended to do this.

It could be made possible to encode a prefetch in the url:

https://www.bahn.de/buchung/fahrplan/suche#sts=true
  &soid=
    <Start: { 
      type: fetch,
      src: https://www.bahn.de/web/api/reiseloesung/orte?suchbegriff=$parameter&typ=ALL&limit=1, 
      jsonpath: [0].id
    } >
  &zoid=
    <Ziel: { fetch: ... >

[mobilutz]

@georgjaehnig I added a comment in the reddit thread: https://www.reddit.com/r/bahn/comments/17kmogj/direktlinks_zur_ergebnissen_der_neuen/

Here is how I think we can solve this:
https://www.bahn.de/buchung/fahrplan/suche#so=Berlin&zo=Hamburg&soid=O%3DBerlin&zoid=O%3DHamburg

soid=O%3DBerlin and zoid=O%3DHamburg

[mobilutz]

PS: The time and date can be added like this:
hd=2024-01-26T10:00:00

I have no idea, how we can keep the same logic as before where trovu has time and date separated. But here some pseudo code:

dbm 3:
  url: 'https://www.bahn.de/buchung/fahrplan/suche#so=<Start: {type: city}>&zo=<Ziel: {type: city}>&soid=O%3D<Start: {type: city}>&zoid=O%3D<Ziel: {type: city}>&hd=<Zeit: {type: time, output: YYYY-MM-DDTHH:mm:ss}>' # time must here be used with the current date

dbm 4:

  url: 'https://www.bahn.de/buchung/fahrplan/suche#so=<Start: {type: city}>&zo=<Ziel: {type: city}>&soid=O%3D<Start: {type: city}>&zoid=O%3D<Ziel: {type: city}>&hd=<Zeit: {type: time, output: YYYY-MM-DDTHH:mm:ss}>' # time must here be used with the forth parameter 😦 

[georgjaehnig]

Thanks for the ideas!

I have no idea, how we can keep the same logic as before where trovu has time and date separated.

That should be no problem, I could implement a position functionality:

hd=<Datum: {position: 4, type: date, output: YYYY-MM-DD}>T<Zeit: {position: 3, type: time, output: HH:mm:ss}>

But for me, some stations are still not working, as I commented on Reddit. Here's a copy:

Danke, das sieht interessant aus! Hab ein paar Städte getestet. Während Berlin-Köln und Berlin-Potsdam klappt, bekomme ich bei Braunschweig keine Verbindung:

https://www.bahn.de/buchung/fahrplan/suche#so=Berlin&zo=Braunschweig&soid=O%3DBerlin&zoid=O%3DBraunschweig

Mit dem Autokennzeichen geht es aber:

https://www.bahn.de/buchung/fahrplan/suche#so=Berlin&zo=Braunschweig&soid=O%3DBerlin&zoid=O%3DBS

Ich vermute, dass bei "Braunschweig" die Auswahl nicht eindeutig genug ist (und er früher da eine Select-Box angezeigt hat). Daher hab ich's mit dem Ausrufezeichen probiert:

https://www.bahn.de/buchung/fahrplan/suche#so=Berlin&zo=Braunschweig&soid=O%3DBerlin&zoid=O%3DBraunschweig%21

aber auch nix.

Vllt. fällt Dir noch was ein. Wie bist Du überhaupt auf diese Möglichkeit gekommen?

[mobilutz]

Strange, I do not see the comment on reddit 😦

So it seems that getting the correct result needs an additional request that must be made.

Looking at what bahn.de does, they make a request to this URL after typing something in the start or end input-field (or unfocusing it)
https://www.bahn.de/web/api/reiseloesung/orte?suchbegriff=_QUERY_&typ=ALL&limit=10

So for Braunschweig it is possible to get the first entry like this:
https://www.bahn.de/web/api/reiseloesung/orte?suchbegriff=braunschweig&typ=ALL&limit=1

Result:

[
  {
    "name":"Braunschweig Hbf",
    "id":"A=1@O=Braunschweig Hbf@X=10540293@Y=52252218@U=80@L=8000049@B=1@p=1706553807@",
    "extId":"8000049",
    "type":"ST"
  }
]

With that result, or more precise with the responses result id entry (URL encoded), the correct request can then be made:
https://www.bahn.de/buchung/fahrplan/suche#so=Berlin&zo=Braunschweig&soid=O%3DBerlin&zoid=A%3D1%40O%3DBraunschweig%20Hbf%40X%3D10540293%40Y%3D52252218%40U%3D80%40L%3D8000049%40B%3D1%40p%3D1706553807%40

This idea is what you already suggested before, and I think the only one to make sure every request works as expected.

[georgjaehnig]

Booking seems to have the same problem now – there, also new type: fetch might help.

[georgjaehnig]

So I revisited this (because of #357), and it seems that (unlike #357) calling

https://www.bahn.de/web/api/reiseloesung/orte?suchbegriff=_QUERY_&typ=ALL&limit=10

does not allow CORS. 😢

It seems one would need to run our own server, providing this API.

[mobilutz]

does not allow CORS.

Mhm, that does not look good. Even when using Postman without any additional headers I get a 400-response 😦

[georgjaehnig]

Experimental fix with #424. See also the blog article. Two problems remain:

1. The userscript is experimental: The search button is not immediately clickable because the page is still loading in the background. Ideally, this would be solved with window.onload or DOMContentLoaded – however, these methods did not work. It is currently resolved with a 4-second setTimeout.
2. The best price search (dbb) still does not work. I have not yet found the appropriate parameter in the URL that displays the best prices immediately upon clicking Search.