On Mon, Jul 24, 2000 at 07:57:00PM +0100, Chris Withers wrote:
Martijn Pieters wrote:
So what was causing the original error then?
Buggy client?
If so, surely Zope should just return an Unauthorized error rather than exposing its internals?!
If you're a server and the client is buggy, tell it so, but don't look like you just screwed up really badly ;-)
Oops. Speed read fumble. We partly agree, and this is tricky. Unauthorised is wrong, it should return a Bad Request (or whatever the correct HTTP error is in this case). File a patch! =) -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ | ZopeStudio: http://www.zope.org/Products/ZopeStudio -----------------------------------------------------