Skip to content

fix: use api enable_https for export download node proxy - #663

Merged
Seechi-Yolo merged 1 commit into
mainfrom
dms/fix-export-download-proxy-scheme
Aug 12, 2026
Merged

fix: use api enable_https for export download node proxy#663
Seechi-Yolo merged 1 commit into
mainfrom
dms/fix-export-download-proxy-scheme

Conversation

@actiontech-bot

@actiontech-bot actiontech-bot commented Aug 12, 2026

Copy link
Copy Markdown
Member

Summary

  • Cross-node data export downloads inferred the proxy scheme from Request.Proto (HTTP version), so targets were always http://. On HTTPS clusters this returned Client sent an HTTP request to an HTTPS server and the UI showed a request error.
  • Derive the inter-node proxy scheme from dms.api.enable_https, use InsecureSkipVerify for internal node TLS, and add download/proxy logging.
  • Add unit tests for scheme selection, HTTPS/HTTP proxy success, scheme mismatch regression, and unreachable peers.

Related CSVW PR: https://github.com/actiontech/dms-ee/pull/959

Test plan

  • go test -mod=vendor -count=1 ./internal/apiserver/service/ -run 'TestNodeProxyScheme|TestProxyDownloadDataExportTask'
  • go vet -mod=vendor ./internal/apiserver/service/
  • make EDITION=ce docker_install
  • After merge, confirm CE→EE sync brings the fix into main-ee

Cross-node data export downloads always built http:// targets from
Request.Proto (HTTP version), so HTTPS clusters failed with 400.
Derive scheme from dms.api.enable_https, skip TLS verify for internal
proxy, and add download proxy logs plus unit tests.
@Seechi-Yolo
Seechi-Yolo merged commit f9be92f into main Aug 12, 2026
1 check passed
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.

3 participants