User documentation
- What is redirection.io?
- Starter's guide
- What are organizations and projects?
- Invite new collaborators
- User account and preferences
- Using traffic logs
- Create a rule
- Triggers and markers reference
- Actions reference
- How to bulk-import or export redirection rules?
- Managing instances
- Project notifications
- Project segmentation
- How much does it cost?
- Can I use redirection.io for free?
- About us
Developer documentation
Agent documentation
- Installing the agent
- Upgrading the agent
- Agent command line options
- The agent as a reverse proxy
- Agent configuration reference
- Minimal configuration
- Listening for requests
- Forwarding requests to the backend
- Virtualhosts
- Trusted proxies
- GeoIP database
- Response compression
- Performance tweaks
- Access logs
- Persisting data in a s3 bucket
- Monitoring the agent
- Using the agent behind a HTTPS proxy
- Agent configuration examples
Managed instances
Crawler
Knowledge base
Legacy versions
The instructions below have been customized for your project "".
Customize these instructions for the project
Response compression
By default, the redirection.io agent does not compress the responses received from the backend servers, and it forwards them to the clients as they are. However, you can configure the agent to compress the responses using gzip or brotli compression algorithms, which can reduce the size of the responses and improve the network performance of your website.
To enable response compression, you can use the http.compress configuration key in the agent configuration file. For example:
instance:
name: 'My Instance'
reverse_proxy:
listen:
- 'tcp://0.0.0.0:80'
forward:
address: 'backend:8080'
agent:
project_key: my-project-key
http:
compress: true