@author Chris Pettitt @version $Revision$

The Request class can be used to construct HTTP request: {@code Request r = new RequestBuilder().setUrl("url") .setRealm((new Realm.RealmBuilder()).setPrincipal(user) .setPassword(admin) .setRealmName("MyRealm") .setScheme(Realm.AuthScheme.DIGEST).build()); r.execute();}

Basic container class to be used for passing requests between nodes. @author Michael Grube

An encapsulation of the request received.

The static method parse() is responsible for creating this object. @author Mark Reinhold @author Brad R. Wetmore @version 1.3, 05/11/17

3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{http://wadl.dev.java.net/2009/02}doc" maxOccurs="unbounded" minOccurs="0"/> <element ref="{http://wadl.dev.java.net/2009/02}param" maxOccurs="unbounded" minOccurs="0"/> <element ref="{http://wadl.dev.java.net/2009/02}representation" maxOccurs="unbounded" minOccurs="0"/> <any processContents='lax' namespace='##other' maxOccurs="unbounded" minOccurs="0"/> </sequence> <anyAttribute processContents='lax' namespace='##other'/> </restriction> </complexContent> </complexType>

@author WS Development Team

A request to the Media Conversion Program for a url that can be used externally to access the transcoded asset for the current device.

Warning: This is a facade provided for use by user code, not for implementation by user code. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.

@mock.generate

A class representing HTTP/HTTPs requests, mapping its all params to class fields.

@author Markus Jevring @since 2007-okt-10 : 13:41:44 @version $Id: Request.java 292 2009-03-04 19:44:36Z jevring $

Request generated by hbm2java

Request model class @author Balazs

This class represents a Request. It can be observed by one or more RequestObservers. A Request can be sent synchronously or asynchronously. By default, a Request is asynchronous upon construction. When a synchronous Request is sent, it will block, causing the current thread to pause while the Request is sent and while waiting for a Response. The RequestObservers that have been added to the Request will not be notified. In most cases, you will not want to send a synchronous Request. When a Request is sent asynchronously, a new thread is created which sends the Request, generates a Response, and notifies any RequestObservers that have been added to the Request. TODO add equals method

An encapsulation of the request received.

The static method parse() is responsible for creating this object. @author Mark Reinhold @author Brad R. Wetmore @version 1.3, 05/11/17

This bean is the model of a layerUpdate request. Is used by the Unredd flows to deserialize the info.xml file provided as a part of the flow input.

etf.org/rfc/rfc3261.txt"> RFC3261:

• ACK - confirms that client has received a final Response to an INVITE Request.
• BYE - indicates to the server that client wishes to release the call leg.
• CANCEL - cancels a pending User Agent Client Request.
• INVITE - indicates that user or service is being invited to participate in a session.
• OPTIONS - queries a server with regards to its capabilities.
• REGISTER - registers contact information with a SIP server.

This specifications also supports the following method name extensions, documented in the following standards track RFCs:

• INFO - used to carry session related control information that is generated during a session. This functionality is defined in RFC2976.
• PRACK - similiar in operation to ACK, however specific to the reliability of provisional Responses. This functionality is defined in RFC3262.
• UPDATE - allows a client to update parameters of a session without impacting the state of a dialog. This functionality is defined in RFC3311.
• SUBSCRIBE - provides an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. This functionality is defined in RFC3265.
• NOTIFY - provides an extensible framework by which SIP nodes can get notification from remote nodes indicating that certain events have occurred. This functionality is defined in RFC3265.
• MESSAGE - for sending instant messages using a metaphor similar to that of a two-way pager or SMS enabled handset. This functionality is defined in RFC3428.
• REFER - requests that the recipient REFER to a resource provided in the request. This functionality is defined in RFC3515.
• PUBLISH - for publishing event state. This functionality is defined in RFC3903.

A valid SIP request formulated by a User Agent Client MUST, at a minimum, contain the following header fields: To, From, CSeq, Call-ID, Max-Forwards, and Via; all of these header fields are mandatory in all SIP requests. These six header fields are the fundamental building blocks of a SIP message, as they jointly provide for most of the critical message routing services including the addressing of messages, the routing of responses, limiting message propagation, ordering of messages, and the unique identification of transactions. These header fields are in addition to the mandatory request line, which contains the method, Request-URI, and SIP version. @author BEA Systems, NIST @version 1.2

3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5">HTTP/1.1, section 10.3.5 for details of the headers that are expected to accompany a {@code 304 Not Modified}response. @author Paul Sandoz @author Marc Hadley @author Marek Potociar @since 1.0

{@link Request} @author suguru

@author Julien Viet

@author Mobius @version $Revision: 1.0 $

Generic request as received from mongrel2. @author Karl Ostendorf

Simplified request @author espinosa

Represents a requested URL along with a count of how many times it has been accessed. @author Simon Brown

The object containing the incoming request to the server.

A request.

A REST request @author Antoine Sabot-Durand

Provides information on the current request.

The request object carries the properties or property ids required to satisfy a resource request. The request object also contains any temporal (date range) information, if any, for each requested property.

Tagging interface that represents all Requests objects that are used on the Cactus client side to store information related to the request that will be sent to the Cactus redirector (on the Cactus Server side). @version $Id: Request.java 238991 2004-05-22 11:34:50Z vmassol $

A Request is the Catalina-internal facade for a ServletRequest that is to be processed, in order to produce the corresponding Response. @author Craig R. McClanahan @version $Revision: 466595 $ $Date: 2006-10-21 23:24:41 +0100 (Sat, 21 Oct 2006) $

Wrapper object for the Coyote request. @author Remy Maucherat @author Craig R. McClanahan @version $Revision: 901 $ $Date: 2009-01-15 10:49:36 -0500 (Thu, 15 Jan 2009) $

Defines an interface to provide client request information . @author Davanum Srinivas @author Carsten Ziegeler @author Berin Loritsch @version CVS $Id: Request.java,v 1.1 2003/03/09 00:09:28 pier Exp $

Defines a request from the end-user to the swing consumer as result of an interaction (e.g. click on hyperlink) of the end-user with the representation of a remote portlet.
Due to the two phase protocol of WSRP this request carries information which need to be passed back to the producer in order to process the interaction at the producer-side.
@author Carsten Ziegeler @author Michel Alessandrini @version $Id: Request.java 264755 2005-08-30 10:29:21Z cziegeler $

This is a low-level, efficient representation of a server request. Most fields are GC-free, expensive operations are delayed until the user code needs the information. Processing is delegated to modules, using a hook mechanism. This class is not intended for user code - it is used internally by tomcat for processing the request in the most efficient way. Users ( servlets ) can access the information using a facade, which provides the high-level view of the request. For lazy evaluation, the request uses the getInfo() hook. The following ids are defined:

• req.encoding - returns the request encoding
• req.attribute - returns a module-specific attribute ( like SSL keys, etc ).

Tomcat defines a number of attributes:

• "org.apache.tomcat.request" - allows access to the low-level request object in trusted applications

@author James Duncan Davidson [duncan@eng.sun.com] @author James Todd [gonzo@eng.sun.com] @author Jason Hunter [jch@eng.sun.com] @author Harish Prabandham @author Alex Cruikshank [alex@epitonic.com] @author Hans Bergsten [hans@gefionsoftware.com] @author Costin Manolache @author Remy Maucherat

Encapsulates a method invocation. @version $Rev: 46019 $ $Date: 2004-09-14 04:56:06 -0500 (Tue, 14 Sep 2004) $

The Request object represents all the information collected from the user when requesting the server do something.

Request received from the client

Request class with convenience with... methods to add headers, parameters etc.

ache.org">Apache MINA Project

Request class with convenience withXxx methods to add headers, parameters, etc.

Generic version of {@link javax.servlet.http.HttpServletRequest}, used to encapsulate the Servlet API version, and to help bridge the differences between Servlet API and Porlet API.

Generic version of {@link javax.servlet.http.HttpServletRequest}, used to encapsulate the Servlet API version, and to help bridge the differences between Servlet API and Porlet API.

The Request service is a {@linkplain org.apache.tapestry5.ioc.services.PropertyShadowBuilder shadow} of the currentthread's request.

Encapsulation of request information. @version $Rev: 1332134 $ $Date: 2012-04-30 05:23:19 -0400 (Mon, 30 Apr 2012) $

This is a low-level, efficient representation of a server request. Most fields are GC-free, expensive operations are delayed until the user code needs the information. Most processing is delegated to modules, using a hook mechanism. This class is not intended for user code - it is used internally by tomcat for processing the request in the most efficient way. Users ( servlets ) can access the information using a facade, which provides the high-level view of the request. For lazy evaluation, the request uses the getInfo() hook. The following ids are defined:

• req.encoding - returns the request encoding
• req.attribute - returns a module-specific attribute ( like SSL keys, etc ).

Tomcat defines a number of attributes:

• "org.apache.tomcat.request" - allows access to the low-level request object in trusted applications

@author James Duncan Davidson [duncan@eng.sun.com] @author James Todd [gonzo@eng.sun.com] @author Jason Hunter [jch@eng.sun.com] @author Harish Prabandham @author Alex Cruikshank [alex@epitonic.com] @author Hans Bergsten [hans@gefionsoftware.com] @author Costin Manolache

Base class for page request implementations allowing access to request parameters. A Request has a URL and a parameter map. You can retrieve the URL of the request with getURL(). The entire parameter map can be retrieved via getParameterMap(). Individual parameters can be retrieved via getParameter(String). If multiple values are available for a given parameter, they can be retrieved via getParameters(String). @author Jonathan Locke

Request object. @author Matej Knopp

This is the structure that represents a request moving through a chain of RequestProcessors. There are various pieces of information that is tacked onto the request as it is processed.

This is the structure that represents a request moving through a chain of RequestProcessors. There are various pieces of information that is tacked onto the request as it is processed.

The Request class can be used to construct HTTP request:

 Request r = new RequestBuilder().setUrl("url") .setRealm((new Realm.RealmBuilder()).setPrincipal(user) .setPassword(admin) .setRealmName("MyRealm") .setScheme(Realm.AuthScheme.DIGEST).build()); 

Base class representing a request to perform an action on the datastore. All requests have 2 methods - constructor and execute. They build an SQL statement, and execute it.

{@link Request} represents a HTTP request, and offers a fluent interface to customizevarious attributes such as the path, the headers, the content, etc.

You can create {@link Request} objects via {@link HttpClient#newRequest(String)} andyou can send them using either {@link #send()} for a blocking semantic, or{@link #send(Response.CompleteListener)} for an asynchronous semantic.

@see Response

Jetty Request.

Implements {@link javax.servlet.http.HttpServletRequest} from the javax.servlet.http package.

The standard interface of mostly getters, is extended with setters so that the request is mutable by the handlers that it is passed to. This allows the request object to be as lightweight as possible and not actually implement any significant behavior. For example

• The {@link Request#getContextPath()} method will return null, until the request has been passed to a {@link ContextHandler} which matches the{@link Request#getPathInfo()} with a context path and calls {@link Request#setContextPath(String)} as a result.
• the HTTP session methods will all return null sessions until such time as a request has been passed to a {@link org.eclipse.jetty.server.session.SessionHandler} which checks for session cookies and enables the ability to create new sessions.
• The {@link Request#getServletPath()} method will return null until the request has been passed to a org.eclipse.jetty.servlet.ServletHandlerand the pathInfo matched against the servlet URL patterns and {@link Request#setServletPath(String)} called as a result.

A request instance is created for each connection accepted by the server and recycled for each HTTP request received via that connection. An effort is made to avoid reparsing headers and cookies that are likely to be the same for requests from the same connection.

The form content that a request can process is limited to protect from Denial of Service attacks. The size in bytes is limited by {@link ContextHandler#getMaxFormContentSize()} or if there is no context then the "org.eclipse.jetty.server.Request.maxFormContentSize" {@link Server}attribute. The number of parameters keys is limited by {@link ContextHandler#getMaxFormKeys()} or if there is no context then the"org.eclipse.jetty.server.Request.maxFormKeys" {@link Server} attribute.

An HTTP request message.

Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.

A Request wraps all of the information needed to invoke a method on a remote object. @author Tim Anderson @version $Revision: 1.3 $ $Date: 2005/04/14 15:08:06 $ @see Response @see Connection

Represents a search request for regions. All predicates will be ORed together. @author jeichar

@author Julien Viet @version $Revision: 1.1 $

A collection of the informations collected and parsed by the {@link Dispatcher} while doing its dispatching work. In case of dispatchingexceptions some fields may be left blank, depending how far the dispatching went. @author Justin DeOliveira @author Andrea Aime

Wrapper object for the Coyote request. @author Remy Maucherat @author Craig R. McClanahan @version $Revision: 1.2 $ $Date: 2007/03/14 02:15:42 $

This represents a reques to gradle that is executed in a separate process using the ProcessLauncherServer. @author mhunsicker

@author Jean Villete

DII requests @author Gerald Brose, FU Berlin @version $Id: Request.java,v 1.29 2009-05-03 21:35:55 andre.spiegel Exp $

The abstract base class for all classes representing requests to be executed against a {@link RepositoryConnection}.

3.org/2001/XMLSchema}anyType"> <sequence> <element name="echoResult" type="{http://www.w3.org/2001/XMLSchema}string" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>

Database compatible workgroup request information.

@author Derek DeMoro

[TODO: document me!] @author Joubin Houshyar (alphazero@sensesay.net) @version alpha.0, 04/02/09 @since alpha.0

A Request is an abstract description of tests to be run. Older versions of JUnit did not need such a concept--tests to be run were described either by classes containing tests or a tree of {@link org.junit.Test}s. However, we want to support filtering and sorting, so we need a more abstract specification than the tests themselves and a richer specification than just the classes.

The flow when JUnit runs tests is that a Request specifies some tests to be run -> a {@link org.junit.runner.Runner} is created for each class implied by the Request ->the {@link org.junit.runner.Runner} returns a detailed {@link org.junit.runner.Description}which is a tree structure of the tests to be run. @since 4.0

Jetty Request.

Implements {@link javax.servlet.HttpServletRequest} from the {@link javax.servlet} package.

The standard interface of mostly getters, is extended with setters so that the request is mutable by the handlers that it is passed to. This allows the request object to be as lightweight as possible and not actually implement any significant behaviour. For example

• The {@link getContextPath} method will return null, until the requeset has been passed to a {@link ContextHandler} which matches the {@link getPathInfo} with a contextpath and calls {@link setContextPath} as a result.
• the HTTP session methods will all return null sessions until such time as a request has been passed to a {@link org.mortbay.jetty.servlet.SessionHandler} which checks for session cookiesand enables the ability to create new sessions.
• The {@link getServletPath} method will return null until the request has beenpassed to a {@link org.mortbay.jetty.servlet.ServletHandler} and the pathInfo matchedagainst the servlet URL patterns and {@link setServletPath} called as a result.

A request instance is created for each {@link HttpConnection} accepted by the server and recycled for each HTTP request received via that connection. An effort is made to avoid reparsing headers and cookies that are likely to be the same for requests from the same connection. @author gregw

Liberty Alliance PAOS Request header.

This interface defines how the SAML1 Request objects behave.

SAML 2.0 ECP Request SOAP header.

OpenSocial data request; encapsulates all information required to execute a request including RESTful URL template, RPC method name, and any parameters required by the provider. Typically, Request objects aren't instantiated by clients directly but are instead returned by service class methods. Requests are executed by passing them into a {@link Client}'s send method. @author Jason Cooper

@author jbarnettTo change the template for this generated type comment go to Window>Preferences>Java>Code Generation>Code and Comments

This class represents a request that can be sent to an HTTP server. @author rdawes

Generic request sent by client connectors. It is then received by server connectors and processed by {@link Restlet}s. This request can also be processed by a chain of Restlets, on both client and server sides. Requests are uniform across all types of connectors, protocols and components. @see org.restlet.Response @see org.restlet.Uniform @author Jerome Louvel

Generic request sent by client connectors. It is then received by server connectors and processed by {@link Restlet}s. This request can also be processed by a chain of Restlets, on both client and server sides. Requests are uniform across all types of connectors, protocols and components. @see org.restlet.client.Response @see org.restlet.client.Uniform @author Jerome Louvel

Represents a single CRUD request on a specific SQL Resource. @author Mark Sawers

Request encapsulates active browser request to the server. @author Nick Belaevski

The Request is used to provide an interface to the HTTP entity body and message header. This provides methods that allow the entity body to be acquired as a stream, string, or if the message is a multipart encoded body, then the individual parts of the request body can be acquired.

This can also maintain data during the request lifecycle as well as the session lifecycle. A Session is made available for convenience. It provides a means for the services to associate data with a given client session, which can be retrieved when there are subsequent requests sent to the server.

It is important to note that the entity body can be read multiple times from the request. Calling getInputStream will start reading from the first byte in the body regardless of the number of times it is called. This allows POST parameters as well as multipart bodies to be read from the stream if desired. @author Niall Gallagher

@since 4.2

Defines a general Request type and provides accessor methods for universal request information.

Also provides access to the HttpRequest that spawned this GeoServer Request. This HttpRequest is most often used to lookup information stored in the Web Container (such as the GeoServer Global information).

@author Rob Hranac, TOPP @author Chris Holmes, TOPP @author Gabriel Roldan @author $Author: Alessio Fabiani (alessio.fabiani@gmail.com) $ (last modification) @author $Author: Simone Giannecchini (simboss1@gmail.com) $ (last modification) @version $Id: Request.java 11513 2009-03-01 04:39:08Z groldan $

this class extends HttpRequestMessage to cope with HTTP request. One subtely here: note how each field acessor never throws an exception, but rather is provided with a default value: this is in the hope that sometime, HTTP will not require all the parsing it requires right now.

The client side idea of a request. Requests are created only by the HttpManager, by cloning its template request that defines the default (application wide) request settings.

@author subwiz

@author subwiz

All possible request for rp @version $Revision$ $Date$

Class Request. @version $Revision$ $Date$

@author Max Zhu (thebbsky@gmail.com)

@author Willie Wheeler (willie.wheeler@gmail.com)

@author Luis Pereira @version 1.0

A request to be handled.

xtensions/xep-0184.html">XEP-0184: Message Delivery Receipts @see XML Schema

Realizes the representation Datalog request. @author art-vybor

Provides information about the HTTP request @author Per Wendel

Represents an HTTP transaction. A new instance is created by the server for each connection.

Provides a set of accessor functions to fetch the individual fields of the HTTP request.

Utility methods that are generically useful for manipulating HTTP requests are included here as well. An instance of this class is passed to handlers. There will be exactly one request object per thead at any time.

The fields {@link #headers}, {@link #query}, and {@link #url}, and the method {@link #getQueryData()}are most often used to examine the content of the request. The field {@link #props}contains information about the server, or up-stream handlers.

The methods {@link #sendResponse(String,String,int)} and{@link Request#sendError(int,String)}are commonly used to return content to the client. The methods {@link #addHeader(String)} and{@link #setStatus(int)} can be used to modify the response headersand return code respectively before the response is sent.

Many of the other methods are used internally, but can be useful to handlers that need finer control over the output that the above methods provide. Note that the order of the methods is important. For instance, the user cannot change the HTTP response headers (by calling the addHeader method or by modifying the responseHeaders field) after having already sent an HTTP response.

A number of the fields in the Request object are public, by design. Many of the methods are convenience methods; the underlying data fields are meant to be accessed for more complicated operations, such as changing the URL or deleting HTTP response headers. @see Handler @see Server @author Stephen Uhler (stephen.uhler@sun.com) @author Colin Stevens (colin.stevens@sun.com) @version 2.6

Manages the request at client-side. @author Flavio Giovarruscio & Riccardo Tribbia @version 1.0

Object contains url to crawl.
It contains some additional information.
@author code4crafter@gmail.com
@since 0.1.0

.ve @author Saul Pina - spina@dcs.net.ve @see Client

@author Makoto YUI (yuin405+xbird@gmail.com)

@author jgroth