IE 5-6 over HTTPS broken downloads
It is known bug of the IE (only) over HTTPS that if any cache control headers were sent before content transfer (specifically file download) then it causes IE error message (can't write to cache - bla-bla-bla) and file download gets aborted. Moreover, as it also known, the HTTPS could not be cached so cache-control headers are useless under HTTPS IMHO. So I propose to check the the env HTTPS (for example) to decide whether to send cache-control headers or not.
Specifically current workaround is to comment out sending cache-control everywhere in code under HTTPS.
Change History
(7)
| Summary: |
IE 5-7 over HTTPS broken downloads → IE 5-6 over HTTPS broken downloads
|
| Keywords: |
windows ie added
|
| Milestone: |
0.8 → 0.9
|
| Priority: |
high → low
|
| Resolution: |
→ duplicate
|
| Status: |
new → closed
|
| Keywords: |
iexplorer added; ie removed
|
Is this IE bug present in the latest IE version, that is, will this problem go away by itself when people upgrade their browsers?