www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Dickow <dic...@uidaho.edu>
Subject general/3322: server corrupting cgi output for octet-streams
Date Sat, 31 Oct 1998 16:37:41 GMT

>Number:         3322
>Category:       general
>Synopsis:       server corrupting cgi output for octet-streams
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Oct 31 08:40:01 PST 1998
>Last-Modified:
>Originator:     dickow@uidaho.edu
>Organization:
apache
>Release:        2.0
>Environment:
Windows95
>Description:
I want to send binary data to the remote client using a CGI
script. But the server is corrupting the data by changing $0A
to $0D, $0A sequences...the newlines for MSDOS machines. My
script explicitly sends a Content-type: application/octet-stream
header. The server also parses out isolated $0D bytes, or messes
them up too. How do I turn this off? ASIS won't do for me in
this particular instance, I don't think. Is there a content-type
that would work?

>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]




Mime
View raw message