THE INFORMATION IN THIS ARTICLE APPLIES TO:
- EFT Enterprise v6 and later
- EFT Standard v6 and later, with HTTP/S module
DISCUSSION
The table below describes errors that can occur during EFT transfers over HTTP/S.
HTTP Error | Cause | Response Body | EftHttpError header |
400 Bad Request | Malformed header, bytes uploaded < content length, or bad query parameter | <html><head><title>Bad Request</title><head><body><H1>HTTP/1.1 400 Bad Request</H1></body></html> | |
401 Unauthorized | Login failed or unknown user agent | <html><head><title>Unauthorized</title><head><body><H1>HTTP/1.1 401 Unauthorized</H1></body></html> | |
403 Forbidden | DELETE when user lacks permission, file locked by another operation, or action denied due to filename restriction | <html><head><title>Forbidden</title><head><body><H1>HTTP/1.1 403 Forbidden</H1></body></html> | “Access+Denied” |
403 Forbidden | GET when user lacks permission, file locked by another operation, or action denied due to filename restriction | Same as above | “Access+Denied” |
403 Forbidden | (MKCOL, MOVE, PUT) when user lacks permission, file locked by another operation, or action denied due to filename restriction (or MOVE non-existent item) | Same as above | “Access+Denied” |
403 Forbidden | Attempt to MKCOL using existing folder name | Same as above | “Exists” |
403 Forbidden | Destination path on server exceeds max length (260) | <html><head><title>Forbidden</title><head><body><H1>HTTP/1.1 403 Forbidden: Path too long</H1></body></html> | "Upload+Path+Too+Long" |
404 Not Found | (DELETE, GET) of non-existent file | <html><head><title>Object Not Found</title><head><body><H1>HTTP/1.1 404 Object Not Found</H1><br/>The requested URL was not found on this server.<br/><hr/></body></html> | |
404 Not Found | CRC failed because file was locked | Same as above | "IOR_RESTRICTED” |
404 Not Found | HEAD on non-existent file/folder | ||
404 Not Found | GET on non-existent folder | ||
406 Not Acceptable | Bad header value, i.e., invalid content range | <html><head><title>Bad Parameter</title><head><body><H1>HTTP/1.1 406 Bad Parameter</H1><br>The requested URL was not found on this server.<br><hr></body></html> | |
408 Request Time-out | Socket timed out on request | ||
411 Length Required | POST with invalid file length (< 0) | ||
412 Precondition Failed | action attempted after session has timed out | <html><head><title>Precondition Failed</title><head><body><H1>HTTP/1.1 412 Precondition Failed</H1></body></html> | |
413 Request Entity Too Large | Attempted GET after download quota reached | <html><head><title>Max Quota Reached</title><head><body><H1>HTTP/1.1 413 Max Quota Reached</H1></body></html> | |
413 Request Entity Too Large | Attempted PUT after the maximum amount of upload data (quota) transferred | <html><head><title>Max Quota Reached</title><head><body><H1>HTTP/1.1 413 Max Quota Reached</H1></body></html> | "Max+Quota+Reached" |
413 Request Entity Too Large | Attempted PUT after the maximum number of uploads performed | Same as above | “Upload+Is+Not+Allowed+By+Transfer+Limits” |
413 Request Entity Too Large | POSTing too large a file | <html><head><title>Request Entity Too Large</title><head><body><H1>HTTP/1.1 413 Request Entity Too Large</H1></body></html> | |
414 Request-URI Too Large | URI exceeds max (4096) length | <html><head><title>Request-URI Too Large</title><head><body><H1>HTTP/1.1 414 Request-URI Too Large</H1></body></html> | |
500 Internal Server Error | Disk full when PUT/POST attempted or unspecified abort of PUT | <html><head><title>Internal Server Error</title><head><body><H1>HTTP/1.1 500 Internal Server Error</H1></body></html> | |
501 Not Implemented | Unimplemented request method or unspecified disk IO error during processing of COPY request | <html><head><title>Not Implemented</title><head><body><H1>HTTP/1.1 501 Not Implemented</H1></body></html> |