> Hi Dirk, > > >>1) Plug quota correctly : > >>Ok to make ContentInterceptor abstract and for UserQuotaContentInterceptor, > >>but what are you meaning by pluggable Interceptors ? > >>Which is the way they should be plugged ? > > > > Today the interceptors can be configured in the domain.xml file > > (NamespaceConfig.java:834) > > UserQuotaContentInterceptor should follow the same principle. > > > Apparently, Remy wishes to rewrite himself the code that plugs > Interceptors to make it more generic. I'm waiting him to commit the code > to plug myself smoothly.
No, that was the functionality I was thinking about. I thought it wasn't implemented yet. > >>4) Null contentLength headers : > >>Are there webdav clients that don't send them ? > >>Allowing such requests processing is a big DOS attack risk. > > > > Make it a configurable option, there will always be clients that > > misbehave allow content with unknown size = true/false > > > +1 > > > Which sort of exception should we throw if this parameter is set to > false and a request have a null contentLength header ? Also using the insufficent storage here looks like a good choice. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
