Closed Bug 102715 Opened 24 years ago Closed 24 years ago

unable to send ftp:// pages

Categories

(MailNews Core :: Composition, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.5

People

(Reporter: tracy, Assigned: mscott)

References

()

Details

(Whiteboard: [PDT-])

seen on recent builds branch and trunk -attempt to Send Page of an ftp:// site the page seems to send with an arror that the ftp://ftp.netscape.com file was not included. reading the received messaged shows the link but not the web page. the link being sent seems link a viable workaround.
triaging.
Assignee: mscott → ducarroz
Component: Networking - General → Composition
QA Contact: huang → sheelar
This works for me in today's nightly (build 2001100214). I suspect that this is a sideeffect of bug 101128. The fix for that went onto the trunk. darin was going to ask about it going on the branch, but I don't know what happened with that.
Also, as a separate bug which will appear in tomorrow's trunk builds - see bug 102826. Summary: ftp files will work, directories will give strange results That bug is not this bug, since it was checked in after this was filed.
seen on commercial trunk builds: windows 2001-10-03-06-trunk linux 2001-10-03-06-trunk mac 2001-10-03-04-trunk okay, the error message on send is gone, but were still failing to send properly as bug 102826 states. marking this fixed and letting the other bug track the remainder of the problem
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
scott, This problem is on the branch build as well. I still see the error dialog using the today's branch build on win98, linux so far. Shouldn't this be fixed on branch as well?
Status: RESOLVED → REOPENED
Keywords: nsbranch
Resolution: FIXED → ---
If you want this fixed on the branch then you need to verify that the patch for bug 101128 is what fixe this, and then take that patch. darin?
I just applied 101128 to the branch and it does indeed fix this problem. I'm able to send and receive ftp pages now. Darin/Bradley, could one of you guys send me a risk assessment for the patch in 101128 if you would be so kind? I'd like to take it to PDT to convince them to take it on the branch. Obviously if you guys think the patch was risky then I would be less inclined to argue for it =).
Assignee: ducarroz → mscott
Status: REOPENED → NEW
Keywords: nsbranchnsbranch+
Target Milestone: --- → mozilla0.9.5
Blocks: 99508
PDT-, bug 101128 will resolve this.
Whiteboard: [PDT-]
Sheela, I just checked 101128 onto the branch. So this bug should be fixed on the branch now.
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Thanks Scott, I will check this on today's branch build.
Branch Builds: 2001-10-04-05 win98, linux, MAC OS X Bug 101128 fix has corrected this problem. I could send page the above url from the browser. I also tried other ftp pages and did not result in any error dialogs as before. The page was sent and received fine. Adding keyword vtrunk to check this on the trunk build later. Since Tracy mentioned in his comments on yesterday's trunk build he did not see the error but the page was not received properly. I will check this again on the trunk later. But today's branch build I received pages the way it should.
Keywords: vtrunk
Unable to verify because of the new regression bug 107568. Bug 107568 should be fixed in order to verify this.
This is still not fixed on the trunk build. I tried a few builds and we still do not display the page inline. We just show the link when it is recieved. Was this really fixed on trunk? Should this be reopened or is this a new regression and I can close this and log a new bug?
Based on the comments in this bug verifying this bug. Because the problem of error while sending is not there any more. Also unable to display the page has been tracked by bug 102826 Marking verified. 2001-11-09-06 win98, linux, mac os x
Status: RESOLVED → VERIFIED
Keywords: vtrunk
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.