Defines an object to assist a service in sending a http response to the client.
Located in /connector/PHRUTS_HttpServiceResponse.php (line 32)
If auto-flush is enabled, any writes are automatically flushed to the client whenever writeln method is called.
The buffer through which all of our output is passed.
The character encoding associated with this Response.
Has the charset been explicitly set.
Boolean indicating if the response has been committed.
The content type associated with this Response.
The set of Cookies associated with this Response.
The HTTP headers explicitly added.
This array is keyed by the header name, and the elements are array containing the associated values that have been set.
The status code for this response.
Adds the specified cookie to the response.
This method can be called multiple times to set more than one cookie.
Adds a response header with the given name and date-value.
The date is specified in terms of milliseconds since the epoch. This method allows response headers to have multiple values.
Add a response header with the given name and value.
This method allows response headers to have multiple values.
Commit the response.
Send headers from the response (status code, cookies and other headers) if the response has not been already committed.
Returns a boolean indicating whether the named response header has already been set.
Encodes the specified URL for use in the sendRedirect method or, if encoding is not needed, returns the URL unchanged.
The implementation of this method includes the logic to determine whether the session ID needs to be encoded in the URL.
Forces any content in the buffer to be written to the client.
A call to this method automatically commits the response, meaning the status code and headers will be written.
Returns the actual auto-flush property for the response.
Returns the actual buffer size used for the response.
Returns the name of the character encoding (MIME charset) used for the body sent in this response.
The character encoding may have been specified explicitly using the setCharacterEncoding or setContentType methods, or implicitly using the setLocale method. Explicit specifications take precedence over implicit specifications. If no character encoding has been specified, ISO-8859-1 is returned.
Returns the content type used for the MIME body sent in this response.
The content type proper must have been specified using setContentType before the response is committed. If no content type has been specified, this method returns null. If a content type has been specified and a character encoding has been explicitly or implicitly specified as described in getCharacterEncoding the charset parameter is uncluded in the string returned. If no character encoding has been specified, the charset parameter is omitted.
Returns a boolean indicating if the response has been committed.
A committed response has already had its status code and headers written.
Clears the content of the underlying buffer in the response without clearing headers or status code.
Sends an error response to the client using the specified status code and clearing the buffer.
The server defaults to creating the response to look like an HTML-formatted server error page containing the specified message, setting the content type to "text/html", leaving cookies and other headers unmodified.
If the response has already been committed, this method throws a PHRUTS_IllegalStateException. After using this method, the response should be considered to be committed an should not be written to.
Sends a temporary redirect response to the client using the specified redirect location URL.
If the response has already been committed, this method throws a PHRUTS_IllegalStateException. After using this method, the response should be considered to be committed an should not be written to.
Sets the auto-flush property for the response.
Sets the character encoding (MIME charset) of the response being sent to the client, for example, to UTF-8.
If the character encoding has already been set by setContentType or setLocale, this method overrides it. Calling setContentType with the string of "text/html" and calling this method with the string of "UTF-8" is equivalent with calling setContentType with the string of "text/html; charset=UTF-8".
Sets the content type of the response being sent to the client, if the response has not been committed yet.
The given content type may include a character encoding specification, for example "text/html;charset=UTF-8".
This method may be called repeatedly to change content type and character encoding. This method has no effect if called after the response has been committed.
Sets a response header with the given name and date-value.
The date is specified in terms of milliseconds since the epoch. If the header had already been set, the new value overwrites the previous one. The containsHeader method can be used to test for the presence of a header before setting its value.
Sets a response header with the given name and value.
If the header had already been set, the new value overwrites the previous one. The containsHeader method can be used to test for the presence of a header before setting its value.
Sets the status code for this response.
This method is used to set the return status code when there is no error (for example, for the status codes SC_OK or SC_MOVED_TEMPORARILY).
If there is an error, and the caller wishes to invoke an error-page defined in the the web application, the sendError method should be used instead.
Clears the buffer, preserving cookies and other headers.
This method prints a string to the buffer response.
This method prints a string to the buffer response.
This method prints a line termination sequence after printing the value.
Status code (202) indicating that a request was accepted for processing, but was not completed.
Status code (502) indicating that the HTTP server received an invalid response from a server it consulted when acting as a proxy or gateway.
Status code (400) indicating the request sent by the client was syntactically incorrect.
Status code (409) indicating that the request could not be completed due to a conflict with the current state of the resource.
Status code (100) indicating the client can continue.
Status code (201) indicating the request succeeded and created a new resource on the server.
Status code (417) indicating that the server could not meet the expectation given in the Expect request header.
Status code (403) indicating the server understood the request but refused to fulfill it.
Status code (302) indicating that the resource reside temporarily under a different URI.
Since the redirection might be altered on occasion, the client should continue to use the Request-URI for future requests(HTTP/1.1). To represent the status code (302), it is recommended to use this variable.
Status code (504) indicating that the server did not receive a timely response from the upstream server while acting as a gateway or proxy.
Status code (410) indicating that the resource is no longer available at the server and no forwarding address is known.
This condition SHOULD be considered permanent.
Status code (505) indicating that the server does not support or refuses to support the HTTP protocol version that was used in the request message.
Status code (500) indicating an error inside the HTTP server which prevented it from fulfilling the request.
Status code (411) indicating that the request cannot be handled without a defined Content-Length.
Status code (405) indicating that the method specified in the Request-Line is not allowed for the resource identified by the Request-URI.
Status code (301) indicating that the resource has permanently moved to a new location, and that future references should use a new URI with their requests.
Status code (302) indicating that the resource has temporarily moved to another location, but that future references should still use the original URI to access the resource.
This definition is being retained for backwards compatibility. SC_FOUND is now the preferred definition.
Status code (300) indicating that the requested resource corresponds to any one of a set of representations, each with its own specific location.
Status code (203) indicating that the meta information presented by the client did not originate from the server.
Status code (406) indicating that the resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Status code (404) indicating that the requested resource is not available.
Status code (501) indicating the HTTP server does not support the functionality needed to fulfill the request.
Status code (304) indicating that a conditional GET operation found that the resource was available and not modified.
Status code (204) indicating that the request succeeded but that there was no new information to return.
Status code (200) indicating the request succeeded normally.
Status code (206) indicating that the server has fulfilled the partial GET request for the resource.
Status code (402) reserved for future use.
Status code (412) indicating that the precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
Status code (407) indicating that the client MUST first authenticate itself with the proxy.
Status code (416) indicating that the server cannot serve the requested byte range.
Status code (413) indicating that the server is refusing to process the request because the request entity is larger than the server is willing or able to process.
Status code (408) indicating that the client did not produce a request within the time that the server was prepared to wait.
Status code (414) indicating that the server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
Status code (205) indicating that the agent SHOULD reset the document view which caused the request to be sent.
Status code (303) indicating that the response to the request can be found under a different URI.
Status code (503) indicating that the HTTP server is temporarily overloaded, and unable to handle the request.
Status code (101) indicating the server is switching protocols according to Upgrade header.
Status code (307) indicating that the requested resource resides temporarily under a different URI.
The temporary URI SHOULD be given by the Location field in the response.
Status code (401) indicating that the request requires HTTP authentication.
Status code (415) indicating that the server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Status code (305) indicating that the requested resource MUST be accessed through the proxy given by the Location field.
Documentation generated on Sat, 31 May 2008 15:46:09 +0200 by phpDocumentor 1.4.1