Datafree Technologies
  • Welcome to Datafree Technologies Docs
  • Connect
    • Connect Product Overview
  • Reach
    • Reach Product Overview
    • Reach Tutorial Videos
    • Steps to Implement Datafree Reach
    • Advanced Topics
    • CORS Support
    • How to Build a Custom Exit Zone Warning Page
    • How to identify Reach traffic
    • Double Encryption in Reach
  • Direct
    • Direct Product Overview
    • Datafree D-Direct
    • D-Direct Failover
    • Information to Collect for a New D-Direct App
    • Network Firewall on Direct
  • Wrap
    • Wrap Product Overview
    • Wrap Best Practices
    • Wrap Daily Limit
  • Switch
    • Switch Product Overview
  • FAQs
    • What is “datafree”?
    • How can I test that my app is datafree?
    • How do I see data usage for my app?
    • What Telcos or MNOs are datafree?
    • What can be made datafree?
Powered by GitBook
On this page
  1. Direct

Datafree D-Direct

PreviousDirect Product OverviewNextD-Direct Failover

Last updated 2 months ago

The new Datafree D-Direct enhancement allows a customer to forward HTTP/S traffic to an endpoint domain or static IP address. Forwarding traffic to a domain gives the customer the flexibility to manage their own domain resolution.Datafree Direct can also pass the client device IPs to the endpoint (origin server) if the customer supports Proxy Protocol. In the case of unencrypted HTTP traffic, we add the device IP to the X-Forwarded-For header.The diagram below shows the traffic flow of Datafree Direct.

If traffic is to be forwarded to a domain, then there must be a public domain (eg. ) and a private domain (eg. ).The Datafree Direct service is extremely low latency, secure (fully encrypted in transit), redundant, highly scalable, with regional failover. Our standard D-Direct service supports traffic on ports 80 and 443. If other ports are needed, please let us know and we can customize your service.

mycompany.com
2345.azure.net