Odd Behavior when moving files

by Tom » Thu, 22 May 2003 01:47:06

When I move a file using drag-and-drop, especially
between computers on my home network, the files become
unusable. If gives me an error "Cannot access read-only
document" or sometimes says "The document name and path
is not valid, Try these suggestions.." None of the
suggestions work. It's as if the files are no longer
accessable.

I read months ago there was a bug in XP that caused
similar problems but have not seen any other
communications.

Can you please let me know if Microsoft has a patch to
fix this problem and how to get it. I don't want to
spend another $35 to get a bug fix.

Thanks,

Tom...

Top

1. IE caching, Odd File Download Text File Behavior?

My WEB Server is sending as part of the HTTP response, the
content-disposition, along with context-type:

Content-Disposition: attachment; filename=4495.TXT
Content-Type: application/octet-stream

yet, IE will intermittently display the file as a TEXT file in a browser
window.

It is odd how it behaves. I can have a list of URLS to download files from
our web server, and the DOWNLOAD prompt will appear consistently as it
should when a user clicks on the URL.

However, there are times that within the DOWNLOAD dialog, if you:

1) CANCEL the download, 3-4 times, or
2) OPEN the file, not SAVE it, where it will appear in a BROWSER (since it
has a TXT extension)

that any new download clicks will always show the file in the browser, no
DOWNLOAD prompts will appear. If I delete the cache, all seems to work
again until I do one of the above again.

It is like IE is ignoring the Content-Disposition and Content-Type once this
cached URL is shown in a browser.

This is causing a inconsistent problems, and for a customer a problem where
they have a service bureau selling information and their customers have the
option to download or view a text file:

.... form data ......
[ ] VIEW ARTICLE (checkbox)
[ PRESS TO DOWNLOAD ARTICLE ]

The user can download the resultant data as a TXT file or view it in a
browser. The difference is how our web server prepares the
context-disposition and context-type.

For downloads, the HTTP response is prepared as

Content-Disposition: attachment; filename=XXXXX.TXT
Content-Type: application/octet-stream

For BRowser views, the HTTP response is prepared as:

Content-type: text/plain

And this worked fine when it was first developed under IE 4.0. But under
5.x and now 6.0, the behavior has changed.

Comments? Input? Advice?

Thanks in advance

--
Hector Santos
Wildcat! Interactive Net Server
http://www.santronics.com

2. auto discovery of printers

3. Search for files and folders odd behaviour

4. XP Home Edition SP1 Crash, no way back?

5. File manager odd behavior