Bug 132276 - improper file name formatting when trying to wget RHEL3 U3 ISO
Summary: improper file name formatting when trying to wget RHEL3 U3 ISO
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-10 15:26 UTC by Chris Stankaitis
Modified: 2008-10-16 19:16 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2008-10-16 19:16:23 UTC


Attachments (Terms of Use)

Description Chris Stankaitis 2004-09-10 15:26:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040806

Description of problem:
As with RHEL3-U2 when you try and wget the RHEL3-U3 ISO the file name
is not being formated properly

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. fish out the ISO URL
2. wget URL
3. see big junky file name
    

Actual Results:  --15:18:44-- 
http://download-2.rhn.redhat.com/download/ak/rhn/isos/rhel-3-u3/rhel-i386-ws-3/rhel-3-U3-i386-ws-disc1.iso?auth=%2F1094915890%2Fbf654901f7b181499c69fcff4b3667c8f5fa49c3%2F1011499%2F9957
           =>
`rhel-3-U3-i386-ws-disc1.iso?auth=%2F1094915890%2Fbf654901f7b181499c69fcff4b3667c8f5fa49c3%2F1011499%2F9957'
Resolving download-2.rhn.redhat.com... done.
Connecting to download-2.rhn.redhat.com[207.61.132.32]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 139,786,240 [application/octet-stream]


 ls:


rhel-3-U3-i386-ws-disc1.iso?auth=%2F1094915890%2Fbf654901f7b181499c69fcff4b3667c8f5fa49c3%2F1011499%2F9957



Expected Results:  wget file, file ends up being named:

rhel-3-U3-i386-ws-disc1.iso

Additional info:

Similar to bug #123576 but not a duplicate given this is U3 and not U2
Though I am sure the same solution to this bug will fix #123576

Comment 1 Chris Stankaitis 2008-08-01 15:28:50 UTC
Please close this bug off it's like 4 years old.  I am sure someone fixed it and
never closed the bug or the issue doesn't exist any more.

Comment 2 Amy Owens 2008-10-16 19:16:23 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.


Note You need to log in before you can comment on or make changes to this bug.