Closed
Bug 492495
Opened 16 years ago
Closed 16 years ago
HTTPS download for image/media on different server fails on Windows+FireFox after cleanup cache and refresh the page
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 480619
People
(Reporter: andy.rivas, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Download fail reported by FireFox when attempting downloads across servers over https;
So right now, only when the combination of below conditions are all met, the problem can repro.
1) FireFox on Windows.
2) Both host page and the image/media are accessed with HTTPS.
3) Host page and image/media are in different server.
4) Must load the page, then cleanup the cache, and refresh the page again in the same secured session.
Reproducible: Always
Steps to Reproduce:
Our example is using XAML with C# code behind.
1) Open a page https://somedomain/somepage
2) Attempt a download https://anotherdomain/someimage.png.
Once the downloading for above image file is done, set the local path as Image's source. (we're programatically changing the xaml image source)
3) Cleanup FireFox's cache.
4) Refresh the page. (refreshing the page should cause you to attempt download again)
Actual Results:
Download failure is reported .
Expected Results:
We expect that the download will be triggered again and succeed.
For the above step 2 if someimage.png comes from the same server as the host page, it just works.
Or if we change both host page and image source's URL to HTTP (instead of HTTPS), it works as well.
It works well on Mac for the same repro steps above.
So right now, only when the combination of below conditions are all met, the problem can repro.
1) FireFox on Windows.
2) Both host page and the image/media are accessed with HTTPS.
3) Host page and image/media are in different server.
4) Must load the page, then cleanup the cache, and refresh the page again in the same secured session.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•