Wicket non-default ajax behavior triggers re-render when component is no longer visible

When a request is issued to a wicket AbstractAjaxBehavior subclass on a component that is invisible, the whole page is re-rendered to a buffer. However, since this is a custom ajax call, the client-side code cannot be expected to deal with the necessary redirects (if it is even possible to detect this scenario on the client).