More strange errors

[Pedro Melo]

Hi,

just two more :)

If I send a notification to a non-existing destination:

HTTP/1.1 200 OK
Connection: close
Date: Sun, 03 Oct 2010 15:18:54 GMT
Server: TwistedWeb/10.1.0
Content-Type: text/html
Client-Date: Sun, 03 Oct 2010 15:18:54 GMT
Client-Peer: 174.143.203.167:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked

[Failure instance: Traceback (failure with no frames): <class
'twisted.web.error.Error'>: 404 Not Found
]

I was expecting the HTTP status code to be 404, not 200.

Same thing with a bad api-key:

HTTP/1.1 200 OK
Connection: close
Date: Sun, 03 Oct 2010 15:20:15 GMT
Server: TwistedWeb/10.1.0
Content-Type: text/html
Client-Date: Sun, 03 Oct 2010 15:20:16 GMT
Client-Peer: 174.143.203.167:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked

[Failure instance: Traceback (failure with no frames): <class
'twisted.web.error.Error'>: 404 Not Found
]

What is the correct way to detect problems like this?

Thanks,
--
Pedro Melo
http://www.simplicidade.org/
xmpp:me...@simplicidade.org
mailto:me...@simplicidade.org

[Jeff Lindsay]

These will be resolved with upcoming upgrades.

--
Jeff Lindsay
http://progrium.com