FlightXML2 maximum redirect reached


#1

Hi guys,

We have been using the flight aware api FlightXML v2 for a while now
and we have noticed that since last friday something has changed at your end and we are getting the following error

{
“error”: “maximum redirect reached at: http://flightaware.com/json/FlightXML2/GetLastTrack?ident=QFA413
}

This error is a bit weird because the API endpoint we hit is actually http://flightxml.flightaware.com/json/FlightXML2/GetLastTrack?ident=QFA413.

Any ideas on what is causing this error? and how can we update the redirect limit?

Thanks,


#2

Also did a curl -iL to the domain and found there is a 302 there to flightaware.com which wasn’t there before.

Also tried http://flightaware.com/json/FlightXML2/GetLastTrack?ident=QFA413 in the browser and it results in a 404.


#3

We’ve attempted to reproduce this issue and we cannot duplicate and errors or redirects. For example, the following works for me from the command-line from an off-network system:

curl 'http://flightxml.flightaware.com/json/FlightXML2/GetLastTrack?ident=QFA413' --user xxxxxxxx:yyyyyyyyyyyyyyyyyyyyyyyyyy

Can you confirm whether you think the error containing “maximum redirect reached at” was the literal JSON that might have been returned by us, or whether your API stack could have been generating that text and returning it wrapped in JSON?

There is one other user in a separate thread also reporting a similar issue, but we are not seeing any significant change in overall user activity in FlightXML2, so this doesn’t seem to be affecting everyone universally.