Hi,
I propose to switch the extension filter off by default, but let the
preferences tunnel by query parameters on by default. The second is also
available in Restlet 1.0 and so it is not required to switch it off, IMO.
To switch the extension tunnel off, you need
getTunnelService().setExtensionTunnel(false).
best regards
Stephan
Alex Milowski schrieb:
I feel like I should be wacking the TunnelService with a rolled up
newspaper. No cookie for you, TunnelService! :)
I just ran into this myself and wasted a bunch of time figuring out
that I needed to turn the tunnel service *OFF*.
It seems to me that the tunnel service shouldn't mess with the
resource reference.
I my case it replaced the return of getRemainingPart() with the same path minus
the final extension. I had a GET request on an XML document and it
not only called
"setExtensions()" along the way but seem to get that wrong in that a call to
getExtensions() returns null. Where did that original extension information go?
This change will also seriously break Atomojo (which uses Restlet).
Good thing that
I know about it and can turn off the TunnelService's want to break my resource
references by :
getTunnelService().setPreferencesTunnel(false);
It seems to me that a service such as this:
* should be *OFF* by default
* shouldn't mess with the original information (e.g. leave the last
segment alone)
* should provide its information as an optional augmentation of the request.
