On Wed, Apr 13, 2005 at 10:47:15AM -0400, Stephan Richter wrote:
> On Thursday 07 April 2005 16:06, Philipp von Weitershausen wrote:
> > > class MethodNotAllowed(Exception):
> > > implements(IMethodNotAllowed)
> > >
> > > def __init__(self, object, request):
> > > self.allow
On Thursday 07 April 2005 16:06, Philipp von Weitershausen wrote:
> > class MethodNotAllowed(Exception):
> > implements(IMethodNotAllowed)
> >
> > def __init__(self, object, request):
> > self.allow = [name for name, adapter
> > in zapi.getAdapters((o
Albertas Agejevas wrote:
On Thu, Apr 07, 2005 at 10:06:38PM +0200, Philipp von Weitershausen wrote:
Albertas Agejevas wrote:
Currently, in the generic case, Zope 3 raises a ComponentLookupError
in zope.app.publication.http line 74, and a 500 response is served.
I can't find that particular line of
On Thu, Apr 07, 2005 at 10:06:38PM +0200, Philipp von Weitershausen wrote:
> Albertas Agejevas wrote:
> >Currently, in the generic case, Zope 3 raises a ComponentLookupError
> >in zope.app.publication.http line 74, and a 500 response is served.
>
> I can't find that particular line of code. Are yo
Albertas Agejevas wrote:
Hi,
I discovered a problem with Zope 3 while developing ReSTive interfaces
for schoolbell, which utilize the HTTPPublication and the
HTTPRequestFactory.
When the user sends a request for a method that is not supported by
the object, the HTTP spec (RFC 2616) mandates respons
