Hi developers, while fixing bug #6173 Jumpers do not comprehend servercontexts I came to the conslusion that there are some more problems because some of the current servlet mappings won't work any more
servjumpers and the JumpersFilter define a jumper like this something might be a jumpers if -there are no dots in the url -the url does not end with / If this is the case jumpers filter and servjumpers search in de jumpers table and if they don't find anything they return the "default" url configured in jumpers.xml This means that /version /mmbase/images/123 /mmexamples all won't work anymore since they are valid (but undefined) jumpers. possible solution: for JumpersFilter it's possible to do a filterChain.doFilter(servletRequest, servletResponse); if no jumper was found . this fixes the problem that /mmbase/images/123 is not wokring anymore for servjumpers it's also possible to just "return" (untested) This solution is not very efficient because every requested image will require a scan over the jumpers table still I think it's a good step to remove the behaviour of the "default" unmatched jumper(by just forwarding) do you agree? [yes] [no] An other additional possible "improvement" is to change the behaviour of the jumpersFIlter so that no "/" are allowed in a jumper do you agree? [yes] [no] -- Kees Jongenburger Mediapark C101 Hilversum +31 (0)35 6772910
