Feature Request: Route to firmware-specific pages to optimize offline cache size and stability

[Zigoman]

Summary

Currently, the offline cache appears to store code/assets for all supported firmware versions at once.

Proposal

Implement an initial landing page (or auto-detection mechanism) that redirects the user to a dedicated page specific to their system's firmware version before triggering the offline cache.

Expected Benefits

• Reduced Cache Size: Users will only cache the specific payload/assets relevant to their firmware version rather than the entire multi-version payload suite.
• Improved Performance & Stability: Smaller cache footprint, faster loading times, and potentially improved exploit success rate/stability due to reduced memory overhead.

Would love to hear your thoughts on whether this architecture is feasible for this host!