On Fri, May 16, 2008 at 12:56 PM, Stephan Koops <[EMAIL PROTECTED]> wrote: > Hi Alex, >> >> I now strongly believe that the TunnelService needs to be off by default. >> > > do you used the most actual version? The extension tunnel is off by default > now.
I just build from the trunk a few minutes ago. Same result. >> >> * the resource reference should remain the same regardless of >> whether such filters are enabled. >> > > IMO no. It is the sense of it, to hide it, if the client used a virtual file > extension or a query parameter for content negotiation, e.g. because no > other way for it is possible or complicate to reach. As said, the extension > tunnel is off by default now, so if you don't switch it on, it will not > change your URI. If yes, than it is bug. Let us know. It isn't working properly then. It still messes with the extension by default. I'd rather see that a developer has to enable the tunnel service to get these features. The simplest story here is that you don't have magic filters getting inserted in your call stack. If you enable the tunnel service, then I could see (based on whatever it is suppose to do), the URI changing. --Alex Milowski
