Redirect HTTP to HTTPS
SkillDev toolshttp-to-https is a skill for AI agents that checks whether a web server redirects all HTTP traffic to HTTPS. It guides the agent through testing the redirect, verifying that paths and query strings are preserved, and fixing the server configuration when the redirect is missing or wrong. It also covers the difference between 301 and 302 redirects and how HSTS removes the need for the redirect on return visits.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load agent skills.
Then ask your AI: use the Redirect HTTP to HTTPS skill
What your AI can do with it
- Test whether http://example.com redirects to https://example.com with a 301 status code
- Check that the full URL path and query string are preserved in the redirect Location heade
- Verify the redirect with curl -I http://example.com
- Explain why HTTP-to-HTTPS redirects are needed and the difference between 301 and 302
- Explain how HSTS can eliminate future HTTP requests for returning users
- Review server config, headers, and forms for responses that violate the rule
Getting started
- Have an AI agent that can load agent skills.
- Add the http-to-https skill to the agent's available skills.
- Have a web server or domain whose HTTP-to-HTTPS redirect you want to check.
- Ask the agent to check whether the server redirects HTTP traffic to HTTPS.
- Follow the agent's fix guidance to configure a 301 redirect and verify it with curl -I.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/http-to-https/SKILL.md and read by ahel’s review.
Without an HTTP-to-HTTPS redirect, users who type the domain without https:// or follow old links land on the insecure version of the site, exposing session cookies and form data to network attackers.
Quick Reference
- Redirect
http://example.comtohttps://example.comwith HTTP 301 (permanent redirect) - Preserve the full path and query string in the redirect:
https://$host$request_uri - Use 301 (not 302) so browsers and search engines cache the redirect and future requests go directly to HTTPS
- Configure redirects at the server/CDN level — never rely on client-side JavaScript for security redirects
- After validating HTTPS works, add HSTS to eliminate future HTTP requests entirely
Check
Test whether http://example.com redirects to https://example.com with a 301 status code. Check that the full URL path and query string are preserved in the redirect Location header.
Fix
Configure the web server to redirect all HTTP requests to HTTPS with a 301 status code, preserving the full request path. Verify the redirect with curl -I http://example.com.
Explain
Explain why redirecting HTTP to HTTPS is necessary, the difference between 301 and 302 redirects, and how HSTS can eliminate the redirect for returning users.
Code Review
Review server config, headers, forms, and integration points related to Redirect HTTP to HTTPS. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/security/http-to-https
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What does this skill check?
- Whether a web server is configured to redirect all HTTP traffic to HTTPS, including that the redirect uses a 301 status code and preserves the full path and query string.
- Why use a 301 instead of a 302 redirect?
- A 301 is a permanent redirect, so browsers and search engines cache it and future requests go directly to HTTPS. A 302 is temporary and does not get cached the same way.
Advanced
- Item type
- skill
- Key
http-to-https- Source
- github.com/thedaviddias/front-end-checklist