Closed Bug 127759 Opened 23 years ago Closed 23 years ago

When publishing via FTP, if the option is set to save images in another directory, the FTP username and password is displayed in the image properties.

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 130149
mozilla1.0

People

(Reporter: dslmichael, Assigned: Brade)

Details

(Whiteboard: publish)

Steps To Reproduce: 1. Launch Composer. 2. Create a simple page with a little bit of text, and an image from your hard drive. 3. Click on File - Publish To to bring up the publish dialog 4. Point to the FTP server of your choice and enter your username and password 5. Give the page a title (if you have not already) and a filename 6. Choose to have the images saved under a different directory on the FTP server (I choose /images/) and click publish 7. View the page off of the server, or download it off of the server and view it locally 8. View the properties of the image Actual Results: The url of the image is now ftp://(username):(password)@(ftpservername)/images/ (imagefilename) Expected Results: I would expect that my username and password not be listed in the image properties. If I change the image URL to be relative to the page location, the image views normally off of the server. So I would expect that if Composer was saving the images to a different location, that it would change the link location respectivly, or at the very least not show my FTP username and password. Another note: If I save the image to the same location as the page, no image is displayed when the file is viewed, and the image properties still show the original location of the file on my harddrive, even though the image file was uploaded. This happens publishing to two different servers both behind the firewall. One is on my Mac running Apache server software on OSX, and the other is on a Linux box using Iplanet server software. I was able to reproduce this problem on the 02-25 trunk build uploading from Win 2k and Win XP.
--> cmanske
Assignee: syd → cmanske
This is a side effect of making the image urls absolute as part of file tranfer. Brade: dup of one of yours, isn't it?
Assignee: cmanske → brade
Severity: normal → major
OS: Windows XP → All
Hardware: PC → All
Whiteboard: publish
Target Milestone: --- → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Keywords: nsbeta1
Target Milestone: mozilla1.2 → mozilla1.0
this dupe should really be the other way but the other bug has the patch, reviews and is waiting for approval to land... <sigh> *** This bug has been marked as a duplicate of 130149 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.