Feature Proposal: DNS improvements

[o-nnerb]

Overview

We're thrilled to introduce a powerful new feature: DNS Override. This feature empowers developers to seamlessly direct specific hosts to alternative hosts during the execution of HTTP requests. We believe this enhancement will greatly amplify the capabilities of RequestDL and streamline the development process for our community.

Implementation Details:

With DNS Override, developers can effortlessly configure host mappings using a simple and intuitive syntax:

DataTask {
    DNSOverride("google.com", to: "g.localhost")
    DNSOverride("apple.com", to: "a.localhost")
    DNSOverride("microsoft.com", to: "microsoft-internal")
}

This configuration enables requests destined for specified hosts to be seamlessly redirected to designated hosts during HTTP request execution. For instance:

• www.google.com will be directed to localhost.
• google.com/?q=HelloWorld will be directed to localhost/?q=HelloWorld.

Benefits:

1. Enhanced Development Flexibility: Developers can now effortlessly simulate diverse network environments and scenarios during application development and testing phases.

2. Fine-Grained Control: DNS Override provides developers with precise control over the routing of network traffic, ensuring more nuanced testing and development processes.

3. Simplified Configuration: The intuitive syntax of DNS Override simplifies configuration and maintenance of DNS mappings, reducing overhead and enhancing productivity.

Final Thoughts:

As we approach the release of RequestDL 3.0.3, we're excited about the possibilities that DNS Override brings to our development ecosystem. We believe this feature will not only streamline development workflows but also foster innovation within our community. We welcome your feedback and suggestions as we strive to deliver a more robust and developer-friendly RequestDL experience.

Milestone: 3.0.3