Modify ↓
Ticket #529 (closed defect: duplicate)
Opened 8 years ago
Last modified 5 years ago
IE 5-6 over HTTPS broken downloads
| Reported by: | tiger@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | general | Version: | 0.7 |
| Severity: | major | Keywords: | windows iexplorer |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
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.
Attachments
Change History
comment:1 Changed 8 years ago by anonymous
- Summary changed from IE 5-7 over HTTPS broken downloads to IE 5-6 over HTTPS broken downloads
comment:2 Changed 8 years ago by daniel
- Milestone set to 0.8
comment:3 Changed 7 years ago by jonas
comment:4 Changed 7 years ago by daniel
- Keywords windows ie added
- Milestone changed from 0.8 to 0.9
- Priority changed from high to low
comment:5 Changed 7 years ago by cmlenz
- Resolution set to duplicate
- Status changed from new to closed
Duplicate of #1020.
comment:6 Changed 7 years ago by mgood
- Milestone 0.9 deleted
comment:7 Changed 5 years ago by sid
- Keywords iexplorer added; ie removed
Note: See
TracTickets for help on using
tickets.
Is this IE bug present in the latest IE version, that is, will this problem go away by itself when people upgrade their browsers?