Closed Bug 141831 Opened 23 years ago Closed 22 years ago

"The file / cannot be found. Please check the location and try again."

Categories

(Core Graveyard :: Networking: FTP, defect)

Product:
Core Graveyard
Component:
Networking: FTP
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 149090
Milestone:
Future

People

(Reporter: benc, Assigned: dougt)

References

(
URL
)

Details

20020502, trunk, Mac OS X (not in Win98, need to check Linux and Mac OS classic) STEPS: Click on URL provided link. OBSERVED: Error message This happens about 50% of the time when I click on the link. If you back and forward arrow, strangely, the page loads correctly. EXPECTED: This link should work w/o problems.
I also have been getting this problem occassionally, even with RC3 (on Mac OS 9.2.2) However I can't use the forward/back buttons or Cmd-LeftArrow/RightArrow to get out of it, in fact I can't even paste in the URL to get it to reload. This only happens with a URL that I've already visited, and won't be accessble again until I quit Moz.
I checked a little into my preferences, and can tell what *doesn't* affect this bug: - Cleared and zeroed both memory and disk caches - Changed cache to never check the page - Turned off Autocomplete - Typed in the URL entirely by hand All of these made no difference, the one page that was stuck still is stuck. In general, I have found this can happen to almost any page, but usually one that I have accessed back and forth, sometimes in two or more tabs, IIRC. Any other testing I could do for this to help nail it down? I've tried everything I can think of.
trace time. only I don't have time...
As discussed in bug 123808, the almost same problem existed for images until bug 149090 was fixed. I am using Mozilla 1.1a, MacOS9. It does not happen when I click Reload lots of times, but if I click on a subdirectory and then Back and Forward a couple of times it happens: Every other time it fails, next time it works again.
I guess this bug is the same as #155973 (the later should be marked as a duplicate) I have the same problem on Mac OS X 10.1.5 and Mozilla 1.0 (Build 2002052918) Try the following two URL's (the behaviour is the same with both): - http://www.tages-anzeiger.ch - http://www.macworld.co.uk 1. Access the page specified by the above mentioned URL 2. Click on a link in the news-ticker 3. Go back to the main page using the BACK-button 4. Click once more on the very same link in the news-ticker 5. Try again to go back using the BACK-button ==> you will get the error message: "The file / cannot be found. Please check the location and try again." This misbehaviour is independent of the settings in the caching policy, will say it occurs when caching is set to: - Every time I view the page - When the page is out of date - Once per session - Never The only workaround is to restart Mozilla which is really annoying especially as this bug occurs with news-ticker sites
Daniel, this bug is about ftp only. Your problem is bug 123808 which was resolved when bug 149090 was fixed in May. Your build is from May ! Please try a newer build. Bug 155973 is invalid.
UPDATE: Mac OS X, classic mode - Mozilla 1.0.1 based commercial build.
I have no time to work on mozilla at the moment, so dougt is taking over FTP open ftp bugs -> him
Assignee: bbaetz → dougt
Target Milestone: --- → Future
check similar symptom on http in bug 167525
RESOLVED/WFM: Mozilla 1.1b.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Well, the problem is still there in Mozilla 1.1 Gecko/20020826 (MacOS9). Unless Benjamin meant 1.2b, it should be reopened.
If you are seeing it, that's enough for me. This happened for me inconsistently for a long time, I actually held of on filing this because I thought I was the only one.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
benc: were you proxying FTP when you observed this? if so, then this is probably a duplicate of the bugs mentioned by biesi.
I am not using a proxy. And I only see it with FTP. Using a fresh profile. Is there an easy way to get a log on macos9, like the NSPR_LOG_FILE settings for dos ? I can consistently reproduce the bug, going to the above ftp link, then clicking back and forward repeatedly. The error message appear on try 3,5,7,9,... That is on the third access, then every other.
I tried all of the URL listed in this bug. I can not reproduce this using the ftp.mozilla.org site. I can not find the "news tickers" in the two sites that are listed in comment #5.
WFM ! Downloaded a nightly 2002100603, and I can't see the bug anymore. Must have been fixed somewhere after 1.1. Thanks to all.
i'm not sure how FTP could ever generate a NS_ERROR_FILE_NOT_FOUND error, since it shouldn't be interacting with the filesystem. HTTP on the other hand uses the disk cache, which has been known to generate a NS_ERROR_FILE_NOT_FOUND error in the past. that's why i asked if FTP was going through a HTTP proxy like squid, but if not... then i have really no idea how this error was ever occuring. guess it's a good thing that is now working :-/
Darin (#14): definitely no proxy, I do proxy tests after I do file and FTP, but I leave my log monitor on. I'm sure stray proxy requests would have caught my eye. I don't think I can rationalize this, but my thinking is that the bug was cache related somehow, just by the feel of when it would happen. This is really my fault, I should have asked tom and gordon for better ideas on how to analyze this as a cache bug a long time ago...
doh! of course, FTP does use the cache for directory listings. and the URL in question is a directory listing. that implies that this is a duplicate of the other bugs. based on when this was reported, it may very well be a duplicate of bug 149090 which i fixed 6/6/2002. marking as a duplicate. please reopen if you're able to repro the problem. *** This bug has been marked as a duplicate of 149090 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
VERIFIED/dupe. I'll reopen here if I see it.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.