Bug 55775

Summary: "Content-Disposition" HTTP header field not supported
Product: [Applications] konqueror Reporter: daniele
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description daniele 2003-03-09 21:09:49 UTC 
Version:            (using KDE KDE 3.1)
Installed from:    Mandrake RPMs

(I've seen there is already a bug marked as new dealing with this issue, but it is two years old! [kde 2.2]).

The http header: "Content-Disposition: attachment; filename=XXX" isn't handled correctly.
 It is quite a problem when you have binary data stored within a database: you can use the content-disposition header field to force a "save as/open with" window, and  provide a name for the file to be saved/opened. 
 Mozilla handles it correctly: it prompts just what I'd expect. 
 Konqueror just ignores it, both with binary and plain text files: if I remove the header, it just behaves the same. 

It is a problem, for example, if you need to open gzipped files stored within a dbms: konqueror automatically calls ark, which complains for the extension of the file is not ".gz", although I have esplicitly defined the file name to be used in the header.

 I'm using mandrake cooker's kde 3.1. 
 
I can't provide a test case as I'm using a local network web application.
Comment 1 daniele 2003-03-09 21:17:57 UTC 
Actually, it seems as the header is correctly interpreted, but not used: for example, I  
 get this prompt for saving a file stored within the DB (I used an extension unknown  
 to the system):  
  
 Open "http://127.0.0.1/~...unti.php?paperId=7" (7_testfile.xcgh)?  
  
 "7_testfile.xcgh" being the name I've forced via the header.  
  
 Still, when I hit "save as", the displayed name is not "7_testfile.xcgh", but 
"visualizzaAppunti.php", which is the name of the script that set the header and 
extracted the contents of the file from the dbms.  
  
 Anyhow, on known filetypes I should be prompted as well, while the default handler  
 is silently used.  
  
 Daniele
Comment 2 Dawit Alemayehu 2003-03-09 22:42:25 UTC 

*** This bug has been marked as a duplicate of 31662 ***