Skip to content

Security: Update HTTP URLs to HTTPS in FDA Clinical Protocol Template#32

Open
yamz8 wants to merge 1 commit into
anthropics:mainfrom
yamz8:fix/update-http-to-https-urls
Open

Security: Update HTTP URLs to HTTPS in FDA Clinical Protocol Template#32
yamz8 wants to merge 1 commit into
anthropics:mainfrom
yamz8:fix/update-http-to-https-urls

Conversation

@yamz8
Copy link
Copy Markdown
Contributor

@yamz8 yamz8 commented Jan 16, 2026

Summary

  • Updated all insecure HTTP URLs to HTTPS for FDA, HHS, and eCFR regulatory links
  • This follows security best practices by ensuring all regulatory documentation references use encrypted connections
  • Total of 24+ URLs updated across FDA, HHS/OHRP, and eCFR domains

Changes

  • ✅ Updated 13+ FDA links from http:// to https://
  • ✅ Updated 8+ HHS/OHRP links from http:// to https://
  • ✅ Updated 3 eCFR links from http:// to https://

Test Plan

  • Verified all HTTP URLs have been converted to HTTPS
  • No HTTP URLs remain in the affected file
  • Manual verification: Spot-check a few updated URLs to ensure they still resolve correctly

Impact

  • Risk Level: Low - URL scheme change only
  • Breaking Changes: None expected - HTTPS endpoints should mirror HTTP endpoints
  • Benefits: Improved security, encrypted connections to all regulatory resources

🤖 Generated with Claude Code

Updated all insecure HTTP URLs to HTTPS for FDA, HHS, and eCFR regulatory links to follow security best practices. This ensures all regulatory documentation references use encrypted connections.

Changes:
- Updated 13+ FDA links from http:// to https://
- Updated 8+ HHS/OHRP links from http:// to https://
- Updated 3 eCFR links from http:// to https://

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant