Edge Application is an Azion product that allows you to build applications that run in Azion’s edge network. By reducing latency and enhancing throughput, Edge Application optimizes your end-user experience by bringing your application closer to them.
By operating on a reverse proxy architecture, Edge Application allows you to create applications on the edge and direct traffic from your domain to Azion. Through this process, your users can effortlessly access your application via a highly distributed global network of edge nodes. Then, Azion selects which edge node closest to the user can handle the request.
Your content or application has to be available from one or several origins. This origin can consist of one or more web servers from your infrastructure, a cloud service, or one of Azion’s Origin services.
With Edge Application, you can:
- Define how your content will be cached.
- Execute functions at the edge.
- Bring your business rules for any request or response.
- Optimize content and image delivery for your users.
- Customize origins and error pages.
You can create and manage edge applications using:
ImplementationSection titled Implementation
|Edge Application first steps||First steps|
|Clone an edge application||How to clone an edge application|
|Delete an edge application||How to delete an edge application|
ModulesSection titled Modules
Modules can complement your implementation of Edge Application. You can enable or disable modules in the Main Settings tab of your application, provided your account supports them and there are no existing dependencies upon deactivation.
See the documentation for each module:
|Application Acceleration||Optimize API protocols and manage dynamic content delivery to accelerate applications and APIs.|
|Edge Caching||Configure cache settings to speed up the delivery of static and dynamic content.|
|Edge Functions||Build ultra-low latency applications and customize content delivery.|
|Image Processor||Optimize image processing for various devices, browsers, and screen resolutions.|
|Load Balancer||Balance traffic between your origin servers and cloud providers to improve fault tolerance and avoid network congestion.|
|L2 Caching||Create a new cache layer between your users and the edge to keep objects in cache for longer periods of time.|
Advanced settingsSection titled Advanced settings
Edge Application allows advanced configuration of origins, cache, functions, error pages, and more, optimizing content delivery for improved performance and user experience.
See the documentation for each available setting:
|Origins||Modify your origin address, |
|Device Groups||Create groups to change your application’s cache and delivery behavior according to end-user devices.|
|Error Responses||Customize error response pages, their cache expiration time, and their origin.|
|Cache Settings||Configure your application’s browser and edge cache expiration time, large file slicing, and advanced cache behavior based on cookies or query strings.|
|Functions||Instantiate functions created with Edge Functions.|
|Rules Engine||Automate the execution of behaviors based on specific parameters for your edge application.|
Delivery ProtocolsSection titled Delivery Protocols
You can customize the delivery of your application by choosing the following options:
- HTTP: delivers your application using only the HTTP protocol.
- HTTP & HTTPS: delivers your application using both the HTTP and HTTPS protocols.
If you choose to deliver your application through HTTP & HTTPS, you must set up digital certificates for your domain.
HTTP/3 supportSection titled HTTP/3 support
If you choose to deliver your application through HTTP & HTTPS, you can enable HTTP/3 support. Based on the QUIC protocol standard, HTTP/3 provides faster load vibes and lower latency when compared to previous versions.
When you enable HTTP/3 support, your edge applications can utilize this protocol version in compatible browsers only through HTTP port 80 and HTTPS port 443.
Upon a user’s first request to an edge application with HTTP/3, the handshake and first response will be conducted using TCP and HTTP/1.1 or HTTP/2. The response from this exchange will assign a value to the Alt-Svc header that indicates that the latest version of the protocol is available to the browser. If the browser supports HTTP/3, the QUIC protocol and HTTP/3 will be used, unless the cached response misses or expires.
PortsSection titled Ports
Azion offers a simultaneous multiport solution, which means you can customize through which HTTP and HTTPS ports your application will be delivered to. You must choose at least one port for each protocol, but you can select from all available ports for delivery.
If you enable HTTP/3 support, multiport configuration will be overwritten to the default ports 80 for HTTP and 443 for HTTPS. Simultaneous multiport isn’t available for applications with HTTP/3 support.
Available portsSection titled Available ports
|HTTP Port||HTTPS Port|
|80 (default)||443 (default)|
Minimum TLS versionSection titled Minimum TLS version
The Transport Layer Security (TLS) protocol allows you to encrypt web traffic. The following TLS versions can be used with edge applications:
- TLS 1.0 (deprecated)
- TLS 1.1 (deprecated)
- TLS 1.2
- TLS 1.3
You can choose the minimum version of TLS that will be supported by your edge application. By choosing recent versions of the protocol, older devices or browsers might not be able to access the edge application.
Azion blocks TLS Renegotiation and TLS Resumption by default. If you want to customize this setup, contact the Sales team.
CiphersSection titled Ciphers
Ciphers are cryptography algorithms utilized to encrypt plaintext into ciphertext, which requires a key to be decrypted. Azion gives you the possibility to change the cipher suite your edge application will use in order to protect your application against TLS attacks.
The cipher suite will determine which cryptographic algorithms will be used in the TLS connections of your edge application. Both, client and server, will negotiate the cipher suite to securely encrypt and decrypt the data exchanged during the session.
The table below shows the ciphers available in each cipher suite.
DomainsSection titled Domains
Azion Domains provides you with the flexibility to use automatically generated domains or your own custom domains, allowing you to manage and deliver content effectively through your edge applications with support for secure connections over HTTP and HTTPS.Learn more about Domains
Digital CertificatesSection titled Digital Certificates
With Digital Certificates, you can enhance the security of your HTTPS applications by binding a custom TLS certificate to your edge application.Learn more about Digital Certificates
Real-Time PurgeSection titled Real-Time Purge
Use Real-Time Purge to clear cached content from Azion’s edge or from the Layer 2 to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your edge application.Learn more about Real-Time Purge
LimitsSection titled Limits
Keepalive timeoutSection titled Keepalive timeout
Azion enforces a keepalive connection duration limit of 10 to 15 minutes between users and edge applications. To avoid the termination of active connections that require more time to complete, consider implementing file slicing or file compression for large files to improve data transfer speeds.