hm I think using the master request is even more strange. so it uses the params of the master request but the generator will calculate the relative path based on the subrequest path because the request context in routing is always updated with the current request. this would be quite inconsistent. so the relative link would still be wrong for the user agent (browser). i guess we should either use the current request attributes here as well and people need to aware what they are doing when using this method in a subrequest.
or we the RoutingListener should only update the routing request context for the master request. I don't see why the routing needs the request context for subrequests.