Class RewriteHandler
- All Implemented Interfaces:
 Handler, Handler.Container, Handler.Singleton, Request.Handler, Container, Destroyable, Dumpable, Dumpable.DumpableContainer, LifeCycle, Invocable
RewriteHandler rewrites incoming requests through a set of Rules.
RewriteHandler can rewrite the request URI, but also HTTP cookies and HTTP headers.
When a rule matches, RewriteHandler can perform actions such as redirect to a
different URI or directly produce a response with a configurable HTTP status code.
Rules can be grouped into a RuleContainer, which is itself a Rule.
If the container rule matches (for example, virtual host name when using
VirtualHostRuleContainer), then the contained rules will be applied.
Rules are applied in the same sequence they are added to the container.
If a rule matches, it applies some logic (typically wrapping the request),
and the next rule is invoked (with the wrapped request), until a
terminating rule is found, or all the rules have
been processed.
Request URI matching is performed either via Servlet pattern matching (using
PatternRule subclasses), via regular expression matching (using
RegexRule subclasses), or by a custom implementation of Rule.
- 
Nested Class Summary
Nested classes/interfaces inherited from class Handler.Abstract
Handler.Abstract.NonBlockingNested classes/interfaces inherited from class AbstractLifeCycle
AbstractLifeCycle.AbstractLifeCycleListener, AbstractLifeCycle.StopExceptionNested classes/interfaces inherited from interface Container
Container.InheritedListener, Container.ListenerNested classes/interfaces inherited from interface Dumpable
Dumpable.DumpableContainer, Dumpable.DumpAppendableNested classes/interfaces inherited from interface Handler
Handler.Abstract, Handler.AbstractContainer, Handler.Collection, Handler.Container, Handler.Sequence, Handler.Singleton, Handler.WrapperNested classes/interfaces inherited from interface Invocable
Invocable.Callable, Invocable.InvocationType, Invocable.ReadyTask, Invocable.TaskNested classes/interfaces inherited from interface LifeCycle
LifeCycle.ListenerNested classes/interfaces inherited from interface Request.Handler
Request.Handler.AbortException - 
Field Summary
Fields inherited from interface Invocable
__nonBlocking, NOOP - 
Constructor Summary
ConstructorsConstructorDescriptionRewriteHandler(RuleContainer rules) RewriteHandler(Handler handler) RewriteHandler(Handler handler, RuleContainer rules)  - 
Method Summary
Modifier and TypeMethodDescriptionvoidAdds aRuleto the existing ones.voidclear()Removes all the rules.Get theRuleContainerused by this handler.getRules()booleanInvoked to handle the passed HTTP request and response.voidsetOriginalPathAttribute(String originalPathAttribute) voidSets the list of rules, discarding the previous ones.Methods inherited from class Handler.Wrapper
getHandler, getInvocationType, setHandlerMethods inherited from class Handler.AbstractContainer
findContainerOf, getDescendant, getDescendants, isDynamic, setDynamic, setServerMethods inherited from class Handler.Abstract
destroy, doStart, doStop, getServerMethods inherited from class ContainerLifeCycle
addBean, addBean, addEventListener, addManaged, contains, dump, dump, dump, dumpObjects, dumpStdErr, getBean, getBeans, getBeans, getContainedBeans, getContainedBeans, installBean, installBean, isAuto, isManaged, isUnmanaged, manage, removeBean, removeBeans, removeEventListener, setBeans, start, stop, unmanage, updateBean, updateBean, updateBeans, updateBeansMethods inherited from class AbstractLifeCycle
getEventListeners, getState, getState, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, setEventListeners, start, stop, toStringMethods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface Container
getCachedBeans, getEventListenersMethods inherited from interface Destroyable
destroyMethods inherited from interface Dumpable.DumpableContainer
isDumpableMethods inherited from interface Handler.Container
getContainer, getDescendant, getDescendants, getDescendantsMethods inherited from interface Handler.Singleton
getHandlers, getTail, insertHandler, setHandlerMethods inherited from interface LifeCycle
addEventListener, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, removeEventListener, start, stop 
- 
Constructor Details
- 
RewriteHandler
public RewriteHandler() - 
RewriteHandler
 - 
RewriteHandler
 - 
RewriteHandler
 
 - 
 - 
Method Details
- 
getRuleContainer
Get theRuleContainerused by this handler.- Returns:
 - the 
RuleContainerused by this handler 
 - 
getRules
 - 
setRules
 - 
addRule
 - 
clear
public void clear()Removes all the rules.
 - 
getOriginalPathAttribute
- See Also:
 
 - 
setOriginalPathAttribute
- See Also:
 
 - 
handle
Description copied from interface:Request.HandlerInvoked to handle the passed HTTP request and response.
The request is accepted by returning true, then handling must be concluded by completing the passed callback. The handling may be asynchronous, i.e. this method may return true and complete the given callback later, possibly from a different thread. If this method returns false, then the callback must not be invoked and any mutation on the response reversed.
Exceptions thrown by this method may be subsequently handled by an error
Request.Handler, if present, otherwise a default HTTP 500 error is generated and the callback completed while writing the error response.The simplest implementation is:
public boolean handle(Request request, Response response, Callback callback) { callback.succeeded(); return true; }A HelloWorld implementation is:
public boolean handle(Request request, Response response, Callback callback) { response.write(true, ByteBuffer.wrap("Hello World\n".getBytes(StandardCharsets.UTF_8)), callback); return true; }- Specified by:
 handlein interfaceRequest.Handler- Overrides:
 handlein classHandler.Wrapper- Parameters:
 request- the HTTP request to handleresponse- the HTTP response to handlecallback- the callback to complete when the handling is complete- Returns:
 - True if and only if the request will be handled, a response generated and the callback eventually called. This may occur within the scope of the call to this method, or asynchronously some time later. If false is returned, then this method must not generate a response, nor complete the callback.
 - Throws:
 Exception- if there is a failure during the handling. Catchers cannot assume that the callback will be called and thus should attempt to complete the request as if a false had been returned.- See Also:
 
 
 -