Legislator Geo Lookup: HTTP Error 502: Bad Gateway

[John Bogil]

I tried to run a legislator geo lookup, here was my request:

openstates.org/api/v1//legislators/geo/?lat=40.712784&long=-74.005941&apikey=[yourAPIkeyhere]

and received this in response:

Piston/0.2.3rc1 (Django 1.6.2) crash report:

Traceback (most recent call last):

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 88, in new_read
    obj = old_read(*args, **kwargs)

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 396, in read
    resp = json.load(urllib2.urlopen(url))

  File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
    return _opener.open(url, data, timeout)

  File "/usr/lib/python2.7/urllib2.py", line 410, in open
    response = meth(req, response)

  File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
    'http', request, response, code, msg, hdrs)

  File "/usr/lib/python2.7/urllib2.py", line 448, in error
    return self._call_chain(*args)

  File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
    result = func(*args)

  File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

HTTPError: HTTP Error 502: Bad Gateway

I didn't see a definition for HTTP Error 502 in the documentation but some quick Googling suggests "Bad Gateway" usually means an error on the server side. Please help!

Thanks,

- John

[Chris Neat]

I'm getting the exact same error in Chicago.

[Chris Neat]

I got the same result

[Andy Lo]

Hi all,

Thanks for alerting us to the issue.  We'll be working on getting the geo lookup endpoints back up and running ASAP.

On Friday, December 4, 2015 at 6:56:07 PM UTC-5, John Bogil wrote:

I tried to run a legislator geo lookup, here was my request:

openstates.org/api/v1//legislators/geo/?lat=40.712784&long=-74.005941&apikey=[yourAPIkeyhere]

and received this in response:

Piston/0.2.3rc1 (Django 1.6.2) crash report:

Traceback (most recent call last):

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 88, in new_read
    obj = old_read(*args, **kwargs)

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 396, in read
    resp = json.load(urllib2.urlopen(url))

  File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
    return _opener.open(url, data, timeout)

  File "/usr/lib/python2.7/urllib2.py", line 410, in open
    response = meth(req, response)

  File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
    'http', request, response, code, msg, hdrs)

  File "/usr/lib/python2.7/urllib2.py", line 448, in error
    return self._call_chain(*args)

  File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
    result = func(*

...

[Andy Lo]

The issue should be resolved now.  Please let us know if the geolocation endpoints continue to present problems.

On Friday, December 4, 2015 at 6:56:07 PM UTC-5, John Bogil wrote:

I tried to run a legislator geo lookup, here was my request:

openstates.org/api/v1//legislators/geo/?lat=40.712784&long=-74.005941&apikey=[yourAPIkeyhere]

and received this in response:

Piston/0.2.3rc1 (Django 1.6.2) crash report:

Traceback (most recent call last):

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 88, in new_read
    obj = old_read(*args, **kwargs)

  File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 396, in read
    resp = json.load(urllib2.urlopen(url))

  File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
    return _opener.open(url, data, timeout)

  File "/usr/lib/python2.7/urllib2.py", line 410, in open
    response = meth(req, response)

  File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
    'http', request, response, code, msg, hdrs)

  File "/usr/lib/python2.7/urllib2.py", line 448, in error
    return self._call_chain(*args)

  File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
    result = func(*

...

[John Bogil]

Thanks for the quick response Andy. Do you think it's worth including this HTTP error code in the documentation for future developers?

--
You received this message because you are subscribed to a topic in the Google Groups "Open State Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fifty-state-project/KoMetrSlMFM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fifty-state-pro...@googlegroups.com.
To post to this group, send email to fifty-sta...@googlegroups.com.
Visit this group at http://groups.google.com/group/fifty-state-project.
For more options, visit https://groups.google.com/d/optout.

[Andy Lo]

The 5xx HTTP error codes are standard error responses indicating server side issues.

To unsubscribe from this group and all its topics, send an email to fifty-state-project+unsub...@googlegroups.com.
To post to this group, send email to fifty-state-project@googlegroups.com.

[John Bogil]

Ahh gotcha, I learned something new. Thanks again

To unsubscribe from this group and all its topics, send an email to fifty-state-pro...@googlegroups.com.
To post to this group, send email to fifty-sta...@googlegroups.com.

Visit this group at http://groups.google.com/group/fifty-state-project.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Open State Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fifty-state-project/KoMetrSlMFM/unsubscribe.

To unsubscribe from this group and all its topics, send an email to fifty-state-pro...@googlegroups.com.
To post to this group, send email to fifty-sta...@googlegroups.com.