Task 3.2: Migrate Commons HTTP Client

Task Description

Replace dot.commons-httpclient with modern HTTP client (org.apache.httpcomponents:httpclient)

Status: 🔄 PENDING

Scope

• Analyze 30+ import statements of Commons HTTPClient
• Evaluate migration to org.apache.httpcomponents:httpclient
• Update HTTP client usage patterns to modern API
• Test all HTTP integrations and external service calls

Implementation Plan

1. Analysis Phase:

   • Review all Commons HTTPClient usage patterns
   • Identify deprecated APIs and modern equivalents
   • Document external service integrations affected

2. Dependency Update:

   • Remove com.dotcms.lib:dot.commons-httpclient from BOM and dotCMS POM
   • Add org.apache.httpcomponents:httpclient to BOM with appropriate version
   • Update dotCMS POM to use modern HTTP client

3. Code Migration:

   • Find all imports: com.dotcms.repackage.org.apache.commons.httpclient.*
   • Replace with: org.apache.http.* (modern API)
   • Update approximately 30+ import statements
   • Migrate deprecated API calls to modern equivalents

4. Testing:

   • Test all HTTP integrations (REST calls, external services)
   • Verify SSL/TLS handling works correctly
   • Check connection pooling and timeout configurations
   • Run integration tests with external services

Acceptance Criteria

• [ ] All HTTP client imports updated to modern API
• [ ] Modern HTTP client dependency added to BOM
• [ ] Repackaged Commons HTTPClient removed from POM files
• [ ] All HTTP integration tests pass
• [ ] No performance regressions in HTTP calls
• [ ] SSL/TLS connections work correctly
• [ ] Connection pooling functions properly

Claude Assistance Benefits

• API Migration: Claude can analyze and update HTTP client API usage patterns
• Pattern Recognition: Identify all HTTP client usage across codebase
• Testing Support: Help identify HTTP integration test cases
• Risk Assessment: Evaluate impact of HTTP client API changes

Related

• Epic: #32675 - Remove Repackaged Dependencies
• Phase: 3 - Medium-Risk Migrations
• Priority: High
• Estimated Effort: 3-4 days (with Claude assistance)

Technical Notes

• Commons HTTPClient is deprecated in favor of modern HTTP components
• API changes may require significant code updates
• Critical for external service integrations
• SSL/TLS handling may need verification
• Connection pooling configurations may need updates

Risk Mitigation

• Comprehensive testing of all HTTP integrations
• Verify external service connections work correctly
• Performance testing for HTTP operations
• Rollback plan for HTTP client changes

Start by locating the BOM and dotCMS POM entries for dot.commons-httpclient, then inventory the 30+ com.dotcms.repackage.org.apache.commons.httpclient imports and their API usage. Run the HTTP integration tests and verify that all imports and dependencies are migrated, external calls, SSL/TLS, timeouts, and pooling still work, and no performance regressions are reported.