Closed Bug 143179 Opened 23 years ago Closed 15 years ago

Copy status bar text or redirected url instead of actual url

Categories

(SeaMonkey :: UI Design, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: a1291762, Assigned: samir_bugzilla)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 Many download sites count downloads by redirecting you to a "counter" URL before you can get the file. They hide this by setting the status bar text to the real URL (so you think it's going to go to the right place). Mozilla can stop this by preventing status bar changes. The problem is that I like to bookmark files for later download, but I don't like having to rely on the download site working when I want to do it. For example, VersionTracker.com does this, but I often find that it's not working when I go to download the files. I would like either: 1) An option to copy the selected link that will automatically follow redirects until it finds a concrete file name. (eg. as a Contextual Menu item) 2) Have an option to copy the status bar text for a link. (eg. as a Contextual Menu item) 3) On the "Open with foo, Save to disk" dialog, have the url in a text field or a "copy URL" button. The last option would also be helpful for bookmarking files on sites that insist on using forms or javascript to launch downloads.
*** This bug has been marked as a duplicate of 168734 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Summary: [RFE] Copy status bar text or redirected url instead of actual url → Copy status bar text or redirected url instead of actual url
This is not the same as that other bug. I'm not asking for the ability to queue downloads. I often copy a bunch of URLs and download them on another computer. I want the ability to copy the *actual* URL of the file. As stated in my initial report, sites often put this URL into the status bar (probably via Javascript). I don't know if Moz can reliably detect and copy that though. The other solution is to request the file (following redirects) until you get a "final" location and copy that.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
FWIW, servers that are really interested in tracking downloads could easily defeat this sort of feature by looking at the HTTP referer. If you did get the actual URL of your download and then visited it later, there would be no referer and the server would simply redirect you elsewhere (front page or a "don't do that" page)
The sort of sites I see doing this the most are places like VersionTracker. They don't offer direct downloads, merely links to other sites so there's no reason to suspect the sites they link to would refuse my download because of a missing referrer header. Often, VT is slow or down but the linked site is fine. If option 1 or 3 (above) is implemented, VT still gets to count my "download" when I copy the URL at work. Option 3 is probably very easy to do as the URL is available (for doing "save", etc).
adding a new feature, requiring new UI to be able to handle the odd case where a site is unfriendly enough to give you the correct URL in the statusbar (via javascript) rather than in the URLbar or on the page seems pretty silly to me. I'm Recommending "wontfix" for this feature request.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Core → Mozilla Application Suite
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.