public class SimpleSessionHandler extends java.lang.Object implements Handler
The following server properties are used:
prefix, suffix, glob, match
MatchString
).
session
extract
In addition to the actual HTTP headers,
the pseudo http headers ipaddress, url, method, and query
are made available for ${...} substitutions.
re
value
re
. The default is "&" , which
uses the entire string "extract" as the session
id.
${...} are substituted (but not \'s) for value
before
looking
for '\n' sequences that are part of the regular expression matches.
digest
value
.
force
Examples:
[prefix].extract=${user-agent} [prefix].re=.*(Netscape|Lynx|MSIE).* [prefix].value=\\1
[prefix].extract=${user-agent}${ipaddress} [prefix].digest=true
[prefix].extract=${Authorization} [prefix].re=code:([0-9]+) [prefix].value=id\\1
Modifier and Type | Field and Description |
---|---|
Regexp |
regexp |
java.lang.String |
valueTemplate |
Constructor and Description |
---|
SimpleSessionHandler() |
public java.lang.String valueTemplate
public Regexp regexp
public boolean init(Server server, java.lang.String prefix)
Handler
init
in interface Handler
server
- The HTTP server that created this Handler
.
Typical Handler
s will use Server.props
to obtain run-time configuration information.prefix
- The handlers name.
The string this Handler
may prepend to all
of the keys that it uses to extract configuration information
from Server.props
. This is set (by the Server
and ChainHandler
) to help avoid configuration parameter
namespace collisions.true
if this Handler
initialized
successfully, false
otherwise. If
false
is returned, this Handler
should not be used.public boolean respond(Request request) throws java.io.IOException
Handler
respond
in interface Handler
request
- The Request
object that represents the HTTP
request.true
if the request was handled. A request was
handled if a response was supplied to the client, typically
by calling Request.sendResponse()
or
Request.sendError
.java.io.IOException
- if there was an I/O error while sending the response to
the client. Typically, in that case, the Server
will (try to) send an error message to the client and then
close the client's connection.
The IOException
should not be used to silently
ignore problems such as being unable to access some
server-side resource (for example getting a
FileNotFoundException
due to not being able
to open a file). In that case, the Handler
's
duty is to turn that IOException
into a
HTTP response indicating, in this case, that a file could
not be found.