# 返回响应（Returning Responses）
[Phalcon\\Http\\Response](http://docs.iphalcon.cn/api/Phalcon_Http_Response.html)是Phalcon中用来处理HTTP响应返回的组件。 HTTP响应通常是由响应头和响应体组成的。下面是一些基本用法:
~~~
<?php
use Phalcon\Http\Response;
// 获取一个响应实例
$response = new Response();
// 设置HTTP状态码
$response->setStatusCode(404, "Not Found");
// 设置响应内容
$response->setContent("Sorry, the page doesn't exist");
// 返回响应到客户端
$response->send();
~~~
If you are using the full MVC stack there is no need to create responses manually. However, if you need to return a response directly from a controller’s action follow this example:
~~~
<?php
use Phalcon\Http\Response;
use Phalcon\Mvc\Controller;
class FeedController extends Controller
{
public function getAction()
{
// Getting a response instance
$response = new Response();
$feed = // ... Load here the feed
// Set the content of the response
$response->setContent(
$feed->asString()
);
// Return the response
return $response;
}
}
~~~
## 使用头部信息（Working with Headers）
在HTTP响应返回中，响应头（Headers）是非常重要的组成部分. 它包含了一些非常有用的信息，比如HTTP状态码，响应类型等等.
你可以使用如下方式来设置头信息:
~~~
<?php
// Setting a header by its name
$response->setHeader("Content-Type", "application/pdf");
$response->setHeader("Content-Disposition", 'attachment; filename="downloaded.pdf"');
// Setting a raw header
$response->setRawHeader("HTTP/1.1 200 OK");
~~~
A[Phalcon\\Http\\Response\\Headers](http://docs.iphalcon.cn/api/Phalcon_Http_Response_Headers.html)bag internally manages headers. This class retrieves the headers before sending it to client:
~~~
<?php
// Get the headers bag
$headers = $response->getHeaders();
// Get a header by its name
$contentType = $headers->get("Content-Type");
~~~
## 重定向（Making Redirections）
可以通过[Phalcon\\Http\\Response](http://docs.iphalcon.cn/api/Phalcon_Http_Response.html)来执行HTTP重定向：
~~~
<?php
// Redirect to the default URI
$response->redirect();
// Redirect to the local base URI
$response->redirect("posts/index");
// Redirect to an external URL
$response->redirect("http://en.wikipedia.org", true);
// Redirect specifying the HTTP status code
$response->redirect("http://www.example.com/new-location", true, 301);
~~~
All internal URIs are generated using the ‘url’ service (by default[Phalcon\\Mvc\\Url](http://docs.iphalcon.cn/reference/url.html)). This example demonstrates how you can redirect using a route you have defined in your application:
所有内部 URIs 都是通过 ‘url’ 来生成的（ 默认是[Phalcon\\Mvc\\Url](http://docs.iphalcon.cn/reference/url.html)）。下面的例子演示如何通过一个应用内预先定义好的路由来重定向。
~~~
<?php
// Redirect based on a named route
return $response->redirect(
[
"for" => "index-lang",
"lang" => "jp",
"controller" => "index",
]
);
~~~
Note that a redirection doesn’t disable the view component, so if there is a view associated with the current action it will be executed anyway. You can disable the view from a controller by executing`$this->view->disable()`;
值得注意的是重定向并不禁用view组件，所以如果当前的action存在一个关联的view的话，将会继续执行它。在控制器中可以通过`$this->view->disable()`来禁用view。
## HTTP 缓存（HTTP Cache）
One of the easiest ways to improve the performance in your applications and reduce the traffic is using HTTP Cache. Most modern browsers support HTTP caching and is one of the reasons why many websites are currently fast.
HTTP Cache can be altered in the following header values sent by the application when serving a page for the first time:
* *Expires:*With this header the application can set a date in the future or the past telling the browser when the page must expire.
* *Cache-Control:*This header allows to specify how much time a page should be considered fresh in the browser.
* *Last-Modified:*This header tells the browser which was the last time the site was updated avoiding page re-loads
* *ETag:*An etag is a unique identifier that must be created including the modification timestamp of the current page
### 设置过期时间（Setting an Expiration Time）
The expiration date is one of the easiest and most effective ways to cache a page in the client (browser). Starting from the current date we add the amount of time the page will be stored in the browser cache. Until this date expires no new content will be requested from the server:
~~~
<?php
$expiryDate = new DateTime();
$expiryDate->modify("+2 months");
$response->setExpires($expiryDate);
~~~
The Response component automatically shows the date in GMT timezone as expected in an Expires header.
If we set this value to a date in the past the browser will always refresh the requested page:
~~~
<?php
$expiryDate = new DateTime();
$expiryDate->modify("-10 minutes");
$response->setExpires($expiryDate);
~~~
Browsers rely on the client’s clock to assess if this date has passed or not. The client clock can be modified to make pages expire and this may represent a limitation for this cache mechanism.
### Cache-Control
This header provides a safer way to cache the pages served. We simply must specify a time in seconds telling the browser how long it must keep the page in its cache:
~~~
<?php
// Starting from now, cache the page for one day
$response->setHeader("Cache-Control", "max-age=86400");
~~~
The opposite effect (avoid page caching) is achieved in this way:
~~~
<?php
// Never cache the served page
$response->setHeader("Cache-Control", "private, max-age=0, must-revalidate");
~~~
### E-Tag
An “entity-tag” or “E-tag” is a unique identifier that helps the browser realize if the page has changed or not between two requests. The identifier must be calculated taking into account that this must change if the previously served content has changed:
~~~
<?php
// Calculate the E-Tag based on the modification time of the latest news
$mostRecentDate = News::maximum(
[
"column" => "created_at"
]
);
$eTag = md5($mostRecentDate);
// Send an E-Tag header
$response->setHeader("E-Tag", $eTag);
~~~
- 简介
- 安装
- 安装(installlation)
- XAMPP下的安装
- WAMP下安装
- Nginx安装说明
- Apache安装说明
- Cherokee 安装说明
- 使用 PHP 内置 web 服务器
- Phalcon 开发工具
- Linux 系统下使用 Phalcon 开发工具
- Mac OS X 系统下使用 Phalcon 开发工具
- Windows 系统下使用 Phalcon 开发工具
- 教程
- 教程 1：让我们通过例子来学习
- 教程 2：INVO简介
- 教程 3: 保护INVO
- 教程4: 使用CRUD
- 教程5: 定制INVO
- 教程 6: Vökuró
- 教程 7：创建简单的 REST API
- 组件
- 依赖注入与服务定位器
- MVC架构
- 使用控制器
- 使用模型
- 模型关系
- 事件与事件管理器
- Behaviors
- 模型元数据
- 事务管理
- 验证数据完整性
- Workingwith Models
- Phalcon查询语言
- 缓存对象关系映射
- 对象文档映射 ODM
- 使用视图
- 视图助手
- 资源文件管理
- Volt 模版引擎
- MVC 应用
- 路由
- 调度控制器
- Micro Applications
- 使用命名空间
- 事件管理器
- Request Environmen
- 返回响应
- Cookie 管理
- 生成 URL 和 路径
- 闪存消息
- 使用 Session 存储数据
- 过滤与清理
- 上下文编码
- 验证Validation
- 表单_Forms
- 读取配置
- 分页 Pagination
- 使用缓存提高性能
- 安全
- 加密与解密 Encryption/Decryption
- 访问控制列表
- 多语言支持
- 类加载器 Class Autoloader
- 日志记录_Logging
- 注释解析器 Annotations Parser
- 命令行应用 Command Line Applications
- Images
- 队列 Queueing
- 数据库抽象层
- 国际化
- 数据库迁移
- 调试应用程序
- 单元测试
- 进阶技巧与延伸阅读
- 提高性能：下一步该做什么？
- Dependency Injection Explained
- Understanding How Phalcon Applications Work
- Api
- Abstract class Phalcon\Acl