Ticket #122 (new enhancement)

Opened 10 months ago

Last modified 7 months ago

supply HTTP status code for server.Encodable objects

Reported by: http://keturn.myopenid.com/ Assigned to:
Priority: minor Milestone:
Keywords: api server encodable Cc:
Project: python-openid OpenID Protocol: All versions
Series: 2.x.x Web Browser:

Description

Right now the logic which says which HTTP status code to send is entangled in Encoder.encode. This is hampering when you want to use an alternate process for that stage.

The only encoding type that is currently at all tricky is the kvform type, which must be 200 for successful responses and 400 for errors.

(We encountered this in our use of the python code, but it's a minor addition to the API that probably could be ported to all ports.)

Change History

05/20/08 14:04:44 changed by http://dag.myopenid.com/

  • priority changed from major to minor.