This implementation has been created to establish a standard between middleware implementations. Applications often need to send requests to external endpoints. To achieve this you can use the Phalcon\Http\Message\Request object. In return, our application will receive back a response object.
NOTE Phalcon does not restrict you in using a specific HTTP Client. Any PSR-7 compliant client will work with this component so that you can perform your requests.
NOTE: In the examples below, $httpClient is the client of your choice which implements PSR-7.
We are creating a new Phalcon\Http\Message\Request object and a new Phalcon\Http\Message\Uri object with the target URL. Following that we define the method (POST) and additional headers that we need to send with our request. The client then sends the request by using the request object.
The above example can be implemented by only using the constructor parameters:
The constructor accepts parameters allowing you to create the object with certain properties populated. You can define the target HTTP method, the URL, the body as well as the headers. All parameters are optional.
method - defaults to GET. The supported methods are: GET, CONNECT, DELETE, HEAD, OPTIONS, PATCH, POST, PUT, TRACE
body - It defaults to php://memory. The method accepts either an object that implements the StreamInterface interface or a string such as the name of the stream. The default mode for the stream is w+b. If a non valid stream is passed, an InvalidArgumentException is thrown
headers - A key value array, with key as the header name and value as the header value.
Returns all of the header values of the given case-insensitive header name as a string concatenated together using a comma. If the string parameter representing the header name requested, an empty string is returned.
Returns an array with all the message header values. The keys represent the header name as it will be sent over the wire, and each value is an array of strings associated with the header. While header names are not case-sensitive, this method preserves the exact case in which headers were originally specified.
<?phpusePhalcon\Http\Message\Request;$jwtToken='abc.def.ghi';$request=newRequest('POST','https://api.phalcon.io/companies/1','php://memory',['Authorization'=>'Bearer '.$jwtToken,'Content-Type'=>'application/json',]);echo$request->getMethod();// POST
Returns the protocol version as as string (default 1.1)
Returns a string representing the message’s request-target either as it will appear (for clients), as it appeared at request (for servers), or as it was specified for the instance (see withRequestTarget()). In most cases, this will be the origin-form of the composed URI, unless a value was provided to the concrete implementation (see withRequestTarget()).
The Request object is immutable. However there are a number of methods that allow you to inject data into it. The returned object is a clone of the original one.
Returns an instance with an additional header appended with the given value. Existing values for the specified header will be maintained. The new value(s) will be appended to the existing list. If the header did not exist previously, it will be added. Throws InvalidArgumentException for invalid header names or values. The header values can be a string or an array of strings.
Returns an instance with the provided value replacing the specified header. While header names are case-insensitive, the casing of the header will be preserved by this function, and returned from getHeaders(). Throws InvalidArgumentException for invalid header names or values.
<?phpusePhalcon\Http\Message\Request;$jwtToken='abc.def.ghi';$request=newRequest('POST','https://api.phalcon.io/companies/1','php://memory',['Authorization'=>'Bearer '.$jwtToken,'Content-Type'=>'application/json',]);echo$request->getMethod();// POST$clone=$request->withMethod('GET');echo$clone->getMethod();// GET
Returns an instance with the specified HTTP protocol version (as string).
Returns an instance with the provided UriInterface URI. This method updates the Host header of the returned request by default if the URI contains a host component. If the URI does not contain a host component, any pre-existing Host header will be carried over to the returned request.
You can opt-in to preserving the original state of the Host header by setting $preserveHost to true. When $preserveHost is set to true, this method interacts with the Host header in the following ways:
If the Host header is missing or empty, and the new URI contains a host component, this method will update the Host header in the returned request.
If the Host header is missing or empty, and the new URI does not contain a host component, this method will not update the Host header in the returned request.
If a Host header is present and non-empty, this method will not update the Host header in the returned request.