861804be5f
This PR was merged into the 2.7 branch. Discussion ---------- URL manipulations as a Twig extension | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | symfony/symfony-docs#4805 While working on the new asset component, I realized that the "absolute URL" feature was misplaced and would benefit from being exposed as a Twig function (composition is always a good thing). Then, I wondered if having a Twig function to generate a relative path (like done by the Routing component would also make sense). And here is the corresponding PR. ```jinja {# generate an absolute URL for the given absolute path #} {{ absolute_url('/me.png') }} {# generate a relative path for the given absolute path (based on the current Request) #} {{ relative_path('/foo/me.png') }} {# compose as you see fit #} {{ absolute_url(asset('me.png')) }} ``` As you can see, we require an absolute path for both functions (and we even add the leading slash if it is omitted), not sure if we want to do otherwise. ping @tobion Commits ------- |
||
---|---|---|
.. | ||
File | ||
Resources/stubs | ||
Session | ||
Tests | ||
.gitignore | ||
AcceptHeader.php | ||
AcceptHeaderItem.php | ||
ApacheRequest.php | ||
BinaryFileResponse.php | ||
CHANGELOG.md | ||
composer.json | ||
Cookie.php | ||
ExpressionRequestMatcher.php | ||
FileBag.php | ||
HeaderBag.php | ||
IpUtils.php | ||
JsonResponse.php | ||
LICENSE | ||
ParameterBag.php | ||
phpunit.xml.dist | ||
README.md | ||
RedirectResponse.php | ||
Request.php | ||
RequestMatcher.php | ||
RequestMatcherInterface.php | ||
RequestStack.php | ||
Response.php | ||
ResponseHeaderBag.php | ||
ServerBag.php | ||
StreamedResponse.php |
HttpFoundation Component
HttpFoundation defines an object-oriented layer for the HTTP specification.
It provides an abstraction for requests, responses, uploaded files, cookies, sessions, ...
In this example, we get a Request object from the current PHP global variables:
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;
$request = Request::createFromGlobals();
echo $request->getPathInfo();
You can also create a Request directly -- that's interesting for unit testing:
$request = Request::create('/?foo=bar', 'GET');
echo $request->getPathInfo();
And here is how to create and send a Response:
$response = new Response('Not Found', 404, array('Content-Type' => 'text/plain'));
$response->send();
The Request and the Response classes have many other methods that implement the HTTP specification.
Loading
If you are not using Composer but are using PHP 5.3.x, you must add the following to your autoloader:
// SessionHandlerInterface
if (!interface_exists('SessionHandlerInterface')) {
$loader->registerPrefixFallback(__DIR__.'/../vendor/symfony/src/Symfony/Component/HttpFoundation/Resources/stubs');
}
Resources
You can run the unit tests with the following command:
$ cd path/to/Symfony/Component/HttpFoundation/
$ composer.phar install
$ phpunit