In versions of XFile prior to version 2.0, setting the UseXLastModifed property to "True" did not result in the creation of the "X-Last-Modified" Request Header as expected. Rather, it appended a "last modified date" parameter to the Content-Disposition header.

   Content-Disposition: form-data; name="FileName1"; filename="C:\testfile.txt"; last modified date="1/9/2004 12:57:10 PM"

The proper format of a header including the "Date Last Modified" file information should be:

   X-Last-Modified: 1/9/2004 12:57:10 PM

As a result, if an upload request is posted with a 1.x release of XFile, FileUp will not be able to parse the "Date Last Modified" information for uploaded files. FileUp's DateLastModified property will be ineffective, but this will not cause scripts to error.

In order for the DateLastModified property of FileUp to be effective when XFile is being used as the client, it is necessary to upgrade XFile to version 2.0 or higher. Version 2.0 and higher will properly create an "X-Last-Modified" header in the upload request.

If, as a work-around, you have developed your own code to parse the "Date Last Modified" information out of the Content-Disposition header, you should be aware that this information will no longer appear in the Content-Disposition header and will only appear as the X-Last-Modified header, as shown above.

Related Links:

• XFile's UseXLastModified property: http://support.softartisans.com/docs/XFile/prog_ref_XFRequest_UseXLastModified.htm
  
  
• FileUp's DateLastModified property: http://support.softartisans.com/docs/FileUpV4/prog_ref_fileup_datelastmodified.htm
  
  
• FileUp's UseDateLastModified property: http://support.softartisans.com/docs/FileUpV4/prog_ref_fileup_usedatelastmodified.htm
  
  
• Upgrading XFile on the client: http://support.softartisans.com/docs/xfile/install_upgrading.htm