[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # HTTP redirect to HTTPS with status code 308 when check my website on MX Toolbox email health 278 views · 3 likes · 7 posts Nnlinh97 (@nnlinh97) · 2024-11-19 ``` http | mysite.com | The remote server returned an error: (308) Permanent Redirect. (http://mysite.com) ``` [this link](https://mxtoolbox.com/emailhealth/horse-trader.co.uk/) I check my site on MX Toolbox and get this error. Please help me how to fix this one? Thanks!! Swarnava Sengupta (@swarnava) · 2024-11-19 Hello, can you send the link how you are testing this? Nnlinh97 (@nnlinh97) · 2024-11-19 [this link](https://mxtoolbox.com/emailhealth/horse-trader.co.uk/) Thank you Swarnava Sengupta (@swarnava) · 2024-11-19 · ♥ 1 Hi, This is because currently horse-trader.co.uk is redirecting to www.horse-trader.co.uk with `308` and mxtoolbox likely doesn't understand the redirect. ``` ➜ ~ curl -I horse-trader.co.uk HTTP/1.0 308 Permanent Redirect Content-Type: text/plain Location: https://horse-trader.co.uk/ Refresh: 0;url=https://horse-trader.co.uk/ server: Vercel ``` You can try setting up `301` redirect which should resolve the issue: https://vercel.com/guides/does-vercel-support-permanent-redirects#other-redirects Nnlinh97 (@nnlinh97) · 2024-11-19 · ♥ 1 [quote="swarnava, post:5, topic:2100"] `curl -I horse-trader.co.uk` [/quote] Hi, thank you for your response I changed to 301 status, and updated redirects in next.config and re-deployed  ``` async redirects() { return [ { source: '/:path*', has: [{ type: 'host', value: 'horse-trader.co.uk' }], destination: 'https://www.horse-trader.co.uk/:path*', permanent: false } ] }, ``` but when run ``` curl -I http://horse-trader.co.uk => 308 !!!! curl -I https://horse-trader.co.uk => 301 ``` Could you help to review these? rh609 (@rh609) · 2024-12-08 · ♥ 1 I'm having a similar problem at the moment whereby I need a http request to go to 301 instead of 308. I managed to have the https request point to 301 by using vercel.json However. I am struggling to do this with http, I've tried Edge Middleware & Serverless functions to force it or intercept headers to get it to somehow be a 301 but no luck. I could be skipping out on core details here, let me know if I am. My conclusion is that it's probably a ME issue, or it could be that Vercel is somehow interfering with the http requests & forcing it to become https resulting in a 308. Carlton (@bigsee) · 2025-04-09 Same issue here! 🙋🏾 I need to find a setup where http://my-domain returns `301` and I have not found a solution yet.
