We currently throw away the departures information from a few of our source feeds, e.g. Trackernet. To do this correctly we would need to ingest that data properly and expose either a new REST endpoint i.e. /StopPoint/{id}/Departures, or as additional properties in the existing /Arrivals response.
1 Like
Yes yes yes. I passed the Accept-Encoding header with my request and that’s so much faster and of course smaller. Luckily for me in iOS it is automatically decompressed so all very easy. Many thanks @Tim
TRACKERNET users - Please make sure you read this post regarding a change to the Trackernet Detailed feed
This error happen for a wide variety of reasons. Normally, this error can be due to a temporary overloading or maintenance being performed on the server and it is resolved after a period of time or once another thread has been released by web-server application. In most cases this could happen (assuming there are no faults in your app) if there are long running tasks and as a result the request queue is backed up.The subsequent points serve as a possible fix, aimed toward resolving the 503 Service Unavailable Error.
- Reload (Refresh) the page
- Scan for Malware
- Visiting the website later
- Contact server admin