Use the same protocol in the JourneyDetailRef as in the ArrivalBoard or DepartureBoard request

[highsource]

Assume we're quierying the arrival board with https:

https://open-api.bahn.de/bin/rest.exe/arrivalBoard?authKey=<KEY>&lang=de&id=008000105&date=2016-02-22&time=15%3a00&format=json

We're still getting JourneyDetailRef with http:

http://open-api.bahn.de/bin/rest.exe/v1.0/journeyDetail?ref=30249%2F14357%2F56420%2F18127%2F80%3Fdate%3D2016-02-22%26station_evaId%3D8000105%26station_type%3Darr%26authKey%3D<KEY>%26lang%3Dde%26format%3Djson%26

So the protocols mismatch. Technically it would be nice to have matching protocols (https in the case above) so that implementations don't jump between HTTP and HTTPS.