THE INFORMATION IN THIS ARTICLE APPLIES TO:
HTTP connection fails when connecting to EFT using CoreFTP:
- When connecting to EFT v6.4.10 via HTTP, CoreFTP receives “No Response Error Loading Directory.”
- When connecting to EFT v6.5.0, CoreFTP receives “HTTP/1.1 400 Bad Request.”
Use EFT Server's Plain-Text client (PTC), Web Transfer Client (WTC), CuteFTP, or other client that supports HTTP 1.1.
Q1: What is CoreFTP doing differently than CuteFTP that is preventing it from connecting to HTTP or HTTPS on EFT?
A1: CoreFTP operates via HTTP 1.0 and sends no Host header, while CuteFTP operates via HTTP 1.1 and sends a Host header. EFT relies on the Host header in redirect and authentication logic.
Q2. Are there any configuration options in EFT that would allow CoreFTP to connect over HTTP or HTTPS?
Q3. Do you know of any configuration options in CoreFTP that would allow CoreFTP to connect over HTTP or HTTPS?
A3. We found no such options. We could not connect to several public Internet sites using CoreFTP (400 Bad Request error). Host header support and lack of HTTP 1.0 support is standard among web server engines.
Optionally provide private feedback to help us improve this article...
Thank you for your feedback!