Home >> All >> org >> mortbay >> [ http Javadoc ]

•	org.mortbay.http.ajp.* (8)	•	org.mortbay.http.ajp.jmx.* (1)	•	org.mortbay.http.handler.* (19)
•	org.mortbay.http.handler.jmx.* (1)	•	org.mortbay.http.ibmjsse.* (1)	•	org.mortbay.http.jmx.* (9)

• org.mortbay.http: Javadoc index of package org.mortbay.http.


Package Samples:

• org.mortbay.http.ajp
• org.mortbay.http.ajp.jmx
• org.mortbay.http.handler
• org.mortbay.http.jmx
• org.mortbay.http.handler.jmx
• org.mortbay.http.ibmjsse

Classes:

• PathMap: URI path map to Object. This mapping implements the path specification recommended in the 2.2 Servlet API. Path specifications can be of the following forms: /foo/bar - an exact path specification. /foo/* - a prefix path specification (must end '/*'). *.ext - a suffix path specification. / - the default path specification. Matching is performed in the following order Exact match. Longest prefix match. Longest suffix match. default. Multiple path specifications can be mapped by providing a list of specifications. The list is separated by the characters specified in the "org.mortbay.http.PathMap.separators" ...
• IPAccessHandler: Handler to authenticate access from certain IP-addresses. A server configuration-XML-file can look something like this: <Configure class="org.mortbay.jetty.Server"> ... <Call name="addContext"> ... <Call name="addHandler"> <Arg> <New class="IPAccessHandler"> <Set name="Standard">deny</Set> <Set name="AllowIP">192.168.0.103</Set> <Set name="AllowIP">192.168.0.100</Set> </New> </Arg> </Call> ... This would deny access for everyone except the requests from the IPs 192.168.0.100 and 192.168.0.103.
• JDBCUserRealm: HashMapped User Realm with JDBC as data source. JDBCUserRealm extends HashUserRealm and adds a method to fetch user information from database. The authenticate() method checks the inherited HashMap for the user. If the user is not found, it will fetch details from the database and populate the inherited HashMap. It then calls the HashUserRealm authenticate() method to perform the actual authentication. Periodically (controlled by configuration parameter), internal hashes are cleared. Caching can be disabled by setting cache refresh interval to zero. Uses one database connection that is initialized ...
• HashUserRealm: HashMapped User Realm. An implementation of UserRealm that stores users and roles in-memory in HashMaps. Typically these maps are populated by calling the load() method or passing a properties resource to the constructor. The format of the properties file is: username: password [,rolename ...] Passwords may be clear text, obfuscated or checksummed. The class com.mortbay.Util.Password should be used to generate obfuscated passwords or password checksums. If DIGEST Authentication is used, the password must be in a recoverable format, either plain text or OBF:. The HashUserRealm also implements SSORealm ...
• HttpContext: Context for a collection of HttpHandlers. HTTP Context provides an ordered container for HttpHandlers that share the same path prefix, filebase, resourcebase and/or classpath. A HttpContext is analagous to a ServletContext in the Servlet API, except that it may contain other types of handler other than servlets. A ClassLoader is created for the context and it uses Thread.currentThread().getContextClassLoader(); as it's parent loader. The class loader is initialized during start(), when a derived context calls initClassLoader() or on the first call to loadClass() Note. that order is important when ...
• HttpOutputStream: HTTP Http OutputStream. Acts as a BufferedOutputStream until setChunking() is called. Once chunking is enabled, the raw stream is chunk encoded as per RFC2616. Implements the following HTTP and Servlet features: Filters for content and transfer encodings. Allows output to be reset if not committed (buffer never flushed). Notification of significant output events for filter triggering, header flushing, etc. This class is not synchronized and should be synchronized explicitly if an instance is used by multiple threads.
• SocketListener: Socket HTTP Listener. The behaviour of the listener can be controlled with the attributues of the ThreadedServer and ThreadPool from which it is derived. Specifically: MinThreads - Minumum threads waiting to service requests. MaxThread - Maximum thread that will service requests. MaxIdleTimeMs - Time for an idle thread to wait for a request or read. LowResourcePersistTimeMs - time in ms that connections will persist if listener is low on resources.
• HttpServer: HTTP Server. Services HTTP requests by maintaining a mapping between a collection of HttpListeners which generate requests and HttpContexts which contain collections of HttpHandlers. This class is configured by API calls. The org.mortbay.jetty.Server class uses XML configuration files to configure instances of this class. The HttpServer implements the BeanContext API so that membership events may be generated for HttpListeners, HttpContexts and WebApplications.
• HttpInputStream: HTTP Chunking InputStream. This FilterInputStream acts as a BufferedInputStream until setChunking(true) is called. Once chunking is enabled, the raw stream is chunk decoded as per RFC2616. The "8859-1" encoding is used on underlying LineInput instance for line based reads from the raw stream. This class is not synchronized and should be synchronized explicitly if an instance is used by multiple threads.
• HttpListener: HTTP Listener. This interface describes the methods of a generic request listener for the HttpServer. Once a HttpListener is started, it is responsible for listening for new connections. Once a new connection is accepted it should be handled by creating a HttpConnection instance and calling either the HttpConnection.handle() or HttpConnection.handleNext() methods from a Thread allocated to that connection.
• HttpConnection: A HTTP Connection. This class provides the generic HTTP handling for a connection to a HTTP server. An instance of HttpConnection is normally created by a HttpListener and then given control in order to run the protocol handling before and after passing a request to the HttpServer of the HttpListener. This class is not synchronized as it should only ever be known to a single thread.
• HttpHandler: HTTP handler. The HTTP Handler interface is implemented by classes that wish to receive and handle requests from the HttpServer. The handle method is called for each request and the handler may ignore, modify or handle the request. Examples of HttpHandler instances include: org.mortbay.http.handler.ResourceHandler org.mortbay.jetty.servlet.ServletHandler
• ContextLoader: ClassLoader for HttpContext. Specializes URLClassLoader with some utility and file mapping methods. This loader defaults to the 2.3 servlet spec behaviour where non system classes are loaded from the classpath in preference to the parent loader. Java2 compliant loading, where the parent loader always has priority, can be selected with the setJava2Complient method.
• InclusiveByteRange: Byte range inclusive of end points. parses the following types of byte ranges: bytes=100-499 bytes=-300 bytes=100- bytes=1-2,2-3,6-,-2 given an entity length, converts range to string bytes 100-499/500 Based on RFC2616 3.12, 14.16, 14.35.1, 14.35.2
• ResourceHandler: Handler to serve files and resources. Serves files from a given resource URL base and implements the GET, HEAD, DELETE, OPTIONS, PUT, MOVE methods and the IfModifiedSince and IfUnmodifiedSince header fields. A simple memory cache is also provided to reduce file I/O. HTTP/1.1 ranges are supported.
• AJP13Listener: AJP 1.3 Protocol Listener. This listener takes requests from the mod_jk or mod_jk2 modules used by web servers such as apache and IIS to forward requests to a servlet container. This code uses the AJP13 code from tomcat3.3 as the protocol specification, but is new implementation.
• ClientCertAuthenticator: Client Certificate Authenticator. This Authenticator uses a client certificate to authenticate the user. Each client certificate supplied is tried against the realm using the Principal name as the username and a string representation of the certificate as the credential.
• HttpFields: HTTP Fields. A collection of HTTP header and or Trailer fields. This class is not synchronized and needs to be protected from concurrent access. This class is not synchronized as it is expected that modifications will only be performed by a single thread.
• HttpRequest: HTTP Request. This class manages the headers, trailers and content streams of a HTTP request. It can be used for receiving or generating requests. This class is not synchronized. It should be explicitly synchronized if it is used by multiple threads.
• IbmJsseListener: SSL Socket Listener for IBM's JSSE. This specialization of JsseListener is an specific listener using the JSSE provider included with the IBM JVMs This is heavily based on the work from Court Demas, which in turn is based on the work from Forge Research.
• HttpResponse: HTTP Response. This class manages the headers, trailers and content streams of a HTTP response. It can be used for receiving or generating requests. This class is not synchronized. It should be explicitly synchronized if it is used by multiple threads.
• JsseListener: JSSE Socket Listener. This specialization of HttpListener is an abstract listener that can be used as the basis for a specific JSSE listener. This is heavily based on the work from Court Demas, which in turn is based on the work from Forge Research.
• HttpTunnel: HTTP Tunnel. A HTTP Tunnel can be used to take over a HTTP connection in order to tunnel another protocol over it. The prime example is the CONNECT method handled by the ProxyHandler to setup a SSL tunnel between the client and the real server.
• SunJsseListener: SSL Socket Listener for Sun's JSSE. This specialization of JsseListener is an specific listener using the Sun reference implementation. This is heavily based on the work from Court Demas, which in turn is based on the work from Forge Research.

Home | Contact Us | Privacy Policy | Terms of Service