GVH: de.schildbach.pte.exception.UnexpectedRedirectException: https://app.efa.de/mdv_server/app_gvh/XSLT_TRIP_REQUEST2?outputFormat=XML&language=de&stateless=1&coordOutputFormat=WGS84[DD.ddddd]&coordOutputFormatTail=7&sessionID=0&requestID=0&coordListOutputFormat=string&type_origin=coord&name_origin=9.7214370%3A52.3675720%3AWGS84%5BDD.ddddd%5D&type_destination=coord&name_destination=9.7204530%3A52.3679780%3AWGS84%5BDD.ddddd%5D&itdDate=20230702&itdTime=1258&itdTripDateTimeDepArr=dep&calcNumberOfTrips=6&ptOptionsActive=1&itOptionsActive=1&routeType=LEASTTIME&changeSpeed=normal&includedMeans=checkbox&inclMOT_0=on&inclMOT_14=on&inclMOT_15=on&inclMOT_16=on&inclMOT_0=on&inclMOT_13=on&inclMOT_18=on&inclMOT_1=on&inclMOT_2=on&inclMOT_3=on&inclMOT_4=on&inclMOT_5=on&inclMOT_6=on&inclMOT_7=on&inclMOT_17=on&inclMOT_19=on&inclMOT_9=on&inclMOT_8=on&inclMOT_10=on&useProxFootSearch=1&trITMOTvalue100=10&locationServerActive=1&useRealtime=1&nextDepsPerLeg=1 -> null about public-transport-enabler

[tinloaf]

That EFA has been updated and the request structure has been changed. The most likely scenario is that for all *.efa.de/ requests, https://app.efa.de/<whatever>/XSLT_WHATEVER_REQUEST… must be changed to https://app.efa.de/efa/XSLT_WHATEVER_REQUEST….

[orcv]

This was fixed in f30b49d

[schildbach]

Ah right, thanks for the heads up.