Database Search
TechHome
 |
- !!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.
iFtpFindNext Problem with Date
Question:
I know that the following disclaimer for the iFtpFindNext is in the Wininet extender help file: Because the FTP protocol provides no standard means of enumerating, some of the common information about files, such as file creation date and time, is not always available or correct. When this happens, iftpFindNext will fill in unavailable information with a "best guess" based on available information. For example, creation and last access dates will often be the same as the file's modification date.my question is: what is the extender using as a "best guesser" protocol?
The reason I ask is because we have little programs that that cycle through all "incoming" directories on our FTP servers and alert us if we have any files out there that are over 12 hours old. We're getting LOTS of weird date/timestamps returned by iFtpFindNext.
for example: 1) a file was received at 4/1/05 at 11:16am. 2) CuteFTP window reports: 4/1/05, 11:16am 3) DOS prompt FTP session reports: Apr 1 11:16 4) iFtpFindNext reports: 2002:09:11:18:00:00
Other times, the date is correct, but the timestamp is 8-10 hours off. We've had this problem for years, but it seems recently that the problem has become more of an issue (perhaps due to updates to FTP servers or something, I don't know). It just seems to me that if DOS always gets good returns, Winbatch should be able to handle it, too. Probably not that simple, though, huh?
Answer:
I believe that the iFtpFindNext function merely gets time in UTC format from WININET and converts the file time to a local file time.Make sure you are using the 'Last write time' when comparing the dates to those other FTP applications.
Article ID: W16889
File Created: 2007:07:03:14:26:44
Last Updated: 2007:07:03:14:26:44