Security · Review & audit
http-to-https
/http-to-https
Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 9
Deprecation
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
Original author description
Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
Original SKILL.md headings · 36 lines, 248 words
SKILL.md preview
--- name: http-to-https description: "Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS." metadata: category: security priority: critical difficulty: beginner estimatedTime: "10" source: frontendchecklist.io url: https://frontendchecklist.io/rules/security/http-to-https --- # Redirect HTTP to HTTPS 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.com` to `https://example.com` with 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/rules/security/http-to-https
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 4 KB
Versions
The database has no other skills named http-to-https.
Database snapshot: 13.11.2026 · package version db47b70ef34a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ssl-https
HTTPS and SSL/TLS audits: certificates, mixed content, HTTPS redirect chains, HSTS and security headers. Use for mixed content, HTTP URLs, certificate issues or HTTP to HTTPS migrations. - 100sitemap-domain
Use when applies to sites that have recently migrated from HTTP to HTTPS, changed domain name, or have www/non-www redirect configurations. Use when sitemap submission reports low coverage. - 100hsts
Use when reviewing HTTP response headers on any site that serves content over HTTPS. - 95zins-analyze-web-traffic
Analyze web traffic patterns using Zscaler Analytics (Z-Insights). Examines traffic distribution by location, protocol breakdown (HTTP vs HTTPS), threat categories, DLP violations, and volume trends over time. Use when an administrator asks: 'Show me web traffic by location',… - 100https-certificate-checker
Validate https certificate checker operations. Auto-activating skill for Security Fundamentals. Triggers on: https certificate checker, https certificate checker Part of the Security Fundamentals skill category. Use when working with https certificate checker functionality.… - 100http-security-headers
Verify and configure HTTP response security headers. Use when reviewing web server configuration, reverse proxy setup, or application middleware that sets response headers.