# \[Help needed\] Windows XP support

**URL:** <https://community.letsencrypt.org/t/help-needed-windows-xp-support/8756>\
**Category:** Uncategorized\
**Created:** [January 12, 2016, 10:43pm UTC](https://community.letsencrypt.org/t/help-needed-windows-xp-support/8756 "2016-01-12T22:43:45Z")\
**Posts on this page:** 1\
**Showing post:** 61

<div class="post-metadata">

**Author:** ![came88](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/came88/32/4398_2.png) [@came88](https://community.letsencrypt.org/u/came88)\
**Post date:** [January 30, 2016, 7:44pm UTC](https://community.letsencrypt.org/t/help-needed-windows-xp-support/8756/61 "2016-01-30T19:44:01Z")

</div>

Any HTTPS-\>HTTP redirect cannot work, because the redirect operate on the HTTP level, on top of all SSL/TSL stuff, and the problem with Windows XP is at this level. If you try this with CURL all seems to work, but only because CURL has a proper SSL/TLS implementation.  
Try with a virtual machine (you can get one for free at [https://dev.windows.com/en-us/microsoft-edge/tools/vms/windows/](https://dev.windows.com/en-us/microsoft-edge/tools/vms/windows/)) and you will see that the redirect will not work.  
The only thing that can work is NOT redirecting windows XP users from HTTP to HTTPS, but if they follow an HTTPS link the browser will display an error for sure.

---

_[View the full topic](https://community.letsencrypt.org/t/help-needed-windows-xp-support/8756)._