Dear all,
thank you all for the feedback.
Now it looks quite clearly like a T-mobile US related problem.
I've send a problem description to T-Mobile, and they have fixed the issue.
So everything should work now properly.
Happy querying,
Roland
___
Dear all,
a user of the OSM readonly mirror Overpass API has complained about getting
always the HTTP error code 504 instead of a valid response with HTTP 200.
After we have excluded all potential obvious problems on both the client and
the server, he still sees the 504 and his requests never
Working fine on ATT.
On Mar 29, 2013 2:57 PM, Roland Olbricht roland.olbri...@gmx.de wrote:
Dear all,
a user of the OSM readonly mirror Overpass API has complained about getting
always the HTTP error code 504 instead of a valid response with HTTP 200.
After we have excluded all potential
Roland,
I could not access it through my T-Mobile serviced device. Time 2:03pm US
Mountain Daylight Time (UTC-06).
Not sure of IP address.
Mike
On Fri, Mar 29, 2013 at 1:59 PM, Clay Smalley claysmal...@gmail.com wrote:
Working fine on ATT.
On Mar 29, 2013 2:57 PM, Roland Olbricht
I couldn't get it either on my t-mobile phone. Same 504 error code.
Location Seattle, WA
On Fri, Mar 29, 2013 at 12:55 PM, Roland Olbricht roland.olbri...@gmx.dewrote:
Dear all,
a user of the OSM readonly mirror Overpass API has complained about getting
always the HTTP error code 504
It may not help much, but it works fine on my t-mobile UK phone. Browser
is firefox.
As a matter of interest, does it work if you use your phones as access
points and use the full computer browser?
Phil (trigpoint)
On Fri, 2013-03-29 at 13:28 -0700, Clifford Snow wrote:
I couldn't get it
Dear all,
thank you very much. Now it looks quite clearly like a T-mobile US related
problem. I do see only very few T-mobile US addresses (all from 208.54.X.X,
although T-mobile has mauch more IPv4 space) in the log files for today. And a
lot of people have just confirmed that the problem
7 matches
Mail list logo
