Hi Alex, The behavior of Directory, with or without the tunnel's extensions feature enabled should be the same.
This looks like a bug to me. Could you provide more details to help us fix that? Best regards, Jerome -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Alex Milowski Envoyé : mardi 13 mai 2008 23:28 À : [email protected] Objet : Re: Troubles with Directory On Tue, May 13, 2008 at 10:49 AM, Alex Milowski <[EMAIL PROTECTED]> wrote: > Oddly enough, with all my uses of Restlet, I haven't really used the Directory > class yet and now that I have, I'm having a bunch of troubles that I just don't > quite understand. > > I have a directory on disk that I'm just trying to "serve up" with the Directory > instance. I have an application that returns a single > instance of "Directory" as its root from createRoot() like this: > > return new Directory(getContext(),LocalReference.createFileReference(dir)); > > where the 'dir' variable is an instance of File initialized to the > content directory. > > When I try to access any file (or directory), I get 300 returns with a > URI list. I've > tried turning content negotiation off but that doesn't seem to help. Looks like this has something to do with the TunnelService and its interaction with extensions. If you either turn off the tunnel service or tell it not to mess with extensions (i.e. setExtensionsTunnel(false)), then Directory works as expected. This leads me to believe there is something not quite so right with what the TunnelService is currently doing with extensions. That is, if I turn on or off the TunnelService and "GET" request on a resource that maps to a file should still work. Again, I'm working with the trunk... :) --Alex Milowski
