Database Search

TechHome

Samples from Users

• !!NEWSFLASH!!
• !Limitations of the WinInet FTP Functions
• !List of Win32 Error Codes
• 12003 ERROR_INTERNET_EXTENDED_ERROR
• 12007 Error
• 12163 error trying to trying to open an FTP session
• Active vs Passive FTP Connections
• Allowing User to Accept Cookies
• Ascii vs Binary FTP Transfers
• Automating Web forms with Cookies
• Can WinInet Handle Framed Pages
• Change Phone Number of Connectiod-Ras entry
• Check for IE4
• Check if a File has been Modified on Web Server
• Check if FTP File Exists
• Check if iUrlOpen returns what your expecting
• Cookies Wont Go Through
• Delete Temporary Internet Files Cache
• Dialog Progress Bar not Working
• Download a Message directly to a Binary buffer
• Embed User Id and Password in URL
• Error 12045 Invalid Certificate
• Error 307 File Access Failed
• Error 321 iFtpFindNext failed
• Error code 632 on WinInet dial-up
• ERROR with iOptionSet
• FTP Directory Exist
• FTP File Exist
• Ftp Functions and OpenVms
• Ftp Issue with Large File Transfers
• FTP Keep Alive
• FTP Proxy Server and Passive Transfer
• FTP SSL
• FtpListFileNames UDF
• Get Wininet Error Description String
• Get Real Internet Address
• Get WinInet Error Description String
• Getting ERROR on iHttpOpen with HTTPS
• Handle Http Redirect
• How to Specifiy HTTP User Agent
• How to use iGetConState
• How to Use iHttpOpen - Do a Post - and Grab HTML
• HTTP and WinInet - An Opus
• HTTPDownload 1.4
• iBegin and Firewalls
• IE4 Dlls needed for Wininet Extender on 95
• iFtpCmd and MDTM command
• iFtpCmd and Quote Site
• iFtpCmd APPE Causes iWriteData to Crash using IE 7
• iFtpCmd APPE Example
• iFtpCmd Issues
• iFtpCmd RETR Crash on Windows 7 32-bit WinInet Only
• iFtpDirMake Error 318
• iFTPFileSize 300 Error FileOpen Failed
• iFtpFindInit Memory Leak
• iFtpFindInit Returns Zero
• iFtpFindInit Wildcards
• iFtpFindNext Problem with Date
• iFtpGet Newer Files Only
• iFtpGet to get INI file
• iFtpGet Wininet Error 12031
• iFtpPut Error 12002 ERROR_INTERNET_TIMEOUT
• iFtpPut Error 12003
• iFtpPut to Unix Server
• iGetConState Return Values
• iGetConState Returns False
• iGetConState(0) Returns 1 for No Connection
• iGetLastError Always Returns 2 with IE5
• iHostConnect and Return Codes
• iHostConnect Error 65535
• iHttpInit and 401 Error
• iHttpOpen Error 406
• iHTTPOpen Error Message 12044 ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED
• iHTTPOpen Not Returning 404
• Installation of a Certificate
• InternetCookieSetEx and InternetCookieGetEx
• iOptionSet Error
• Latitude and Longitude of An Address
• Logfile of FTP Session
• Make a WHOIS Request
• Multiple FTP Sessions
• Non Standard Port
• Post HTML Problem
• Print a Web Page
• Progress bar during HTTP download
• Removing Empty Directories with FTP
• Require Certificate for HTTPS Downloads
• Return Info on Web Server
• Sample code - Weather Watch
• Secure FTP Issues
• Select Links That Contain Java Script Code
• Syncronize FTP
• UrlEncode of Hebrew characters
• Website Forms with Viewstate and Eventvalidation
• Wininet and Cookies
• WinInet and JavaScript
• WinInet and OpenVMS Problem
• WinInet Errors
• WinInet Not Supported for Use in Services
• Yahoo Signin Form

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

!Limitations of the WinInet FTP Functions

 Keywords:  

Limitations of WinInet FTP Functions

There are some known limitations to the WinInet FTP functions to be aware of. Before deciding to rely on WinInet for an application's FTP functionality, you should verify that the FTP functions work as expected with all required FTP servers.

Note: WinInet does not directly implement all of the functionality available through the FTP protocol. Most of the common activities such as uploading, downloading, renaming and deleting files, as well as enumerating directories, are available in this extender. However there are a number of other FTP commands that are not implemented directly, such as ACCOUNT, QUOTE, APPEND, BLOCK and ALLOCATE.

Beginning with Internet Explorer version 5.0 there is a new WinInet function, iFtpCmd, which allows you to functionally implement your own QUOTE command and send a specific command to the server. Previous versions of WinInet had no ability to send specific commands to the FTP server.

WinInet may have problems with some FTP servers. The FTP protocol is designed with the presumption that the output is viewed and viewed by a user, who can interpret the reply code and text.

WinInet FTP attempts to parse and interpret the reply. If an FTP server returns a nonstandard reply to WinInet, then WinInet may not be able to function properly. In addition, some servers may require a sequence of commands which is incompatible with WinInet. For instance, some servers require an account command be entered immediately upon logging on. Although you could enter an account (ACCT) command using the iFtpCmd function after you have already logged on, the FTP logon sequence implemented by WinInet is not flexible enough to enter an account (ACCT) command if required immediately by the server.

More Information
The following are a couple of instances where problems are known to occur. This is not a complete list, and you may encounter additional limitations not listed here.

VMS FTP servers:
WinInet FTP functions may not work with some FTP servers running on the VMS operating system. In particular, the FTP functions may fail with an error, or the data structure that returns file information may be blank or contain invalid data. For additional information, please see the following article in the Microsoft Knowledge Base:

Q168492 PRB: FTP WinInet APIs Report Error 12003

This problem occurs when text returned by the FTP server is in a format that WinInet cannot parse correctly. You can work around this problem by using the iFtpCmd function and sending a LIST command to the server. You could then either display the listing results in your application directly, or parse the returned data yourself.

Firewalls:
Although WinInet FTP APIs are designed to work with FTP Gateway, functionality may be severely affected when CERN type proxy is used (iFtpPut, iFtpGet, etc. may not work correctly). Limited FTP functionality may be achieved over a CERN proxy with the iUrlOpen function. Additional issues may also arise if proxy requires a user name and password different than the user name and password required by the destination FTP server. For additional information on using FTP through a CERN proxy, please see the following articles in the Microsoft Knowledge Base:

Q166961 HOWTO: FTP with CERN-Based Proxy Using WinInet API

Q216214 SAMPLE: FTP with CERN-Based Password Protected Proxy

Article ID:   W15092

File Created: 2003:02:11:12:44:08

Last Updated: 2003:02:11:12:44:08