From nobody@hyperreal.com Fri Feb 21 18:46:42 1997 Received: by taz.hyperreal.com (8.8.4/V2.0) id SAA18922; Fri, 21 Feb 1997 18:46:42 -0800 (PST) Message-Id: <199702220246.SAA18922@taz.hyperreal.com> Date: Fri, 21 Feb 1997 18:46:42 -0800 (PST) From: Lou Duchez Reply-To: ljduchez@en.com To: apbugs@hyperreal.com Subject: Filename in "Content-Disposition" ignored -- script name used instead X-Send-Pr-Version: 3.2 >Number: 184 >Category: mod_cgi >Synopsis: Filename in "Content-Disposition" ignored -- script name used instead >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Feb 21 18:50:00 1997 >Last-Modified: Mon Mar 31 07:32:28 PST 1997 >Originator: ljduchez@en.com >Organization: >Release: 1.2b4 >Environment: BSDI Unix >Description: I freely admit that I am a novice at CGI scripting, PERL, and higher level HTML coding. So it's possible I'm doing something wrong here, but I cannot find any problem in my code. I have a PERL script to send documents to users via "Content-type: application/octet-stream", with a "Content-disposition: filename=whatever" line immediately following. The name that is suggested to the user when the file is received, is not "whatever", but the name of the script that created the HTML code. >How-To-Repeat: Please examine: http://www.en.com/users/ljduchez/cgi-bin/sendbin.pl, a generic PERL script to send files to users. You may call this PERL script from http://www.en.com/users/ljduchez/sendbin.html; when the selected file is sent, it will take on the name "sendbin.pl". >Fix: >Audit-Trail: State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Tue Feb 25 12:35:37 PST 1997 State-Changed-Why: This doesn't seem like a server problem; it seems to me that some clients simply don't listen to it. There is nothing the server can do about it. Do you have any reason for thinking it is a server problem? State-Changed-From-To: analyzed-closed State-Changed-By: coar@decus.org State-Changed-When: Mon Mar 31 07:32:28 PST 1997 State-Changed-Why: If *any* browsers are working properly and reproducibly with this information, then the server is sending it correctly and the problem lies with the browsers. The script pages you reference no longer exist, and you say that Mozilla works reliably with this construct, so it appears that this *is* a browser problem and you have found a workaround. Thank you for using Apache! >Unformatted: Further information from the submitter from from PR#185: Further information: the bug does not seem to occur in Netscape. It DOES occur in Lynx, Microsoft Internet Explorer, and Opera.