Postscript Behavior...firstname.lastname@example.org (Marc Andreessen)
Date: Tue, 27 Apr 93 17:45:19 -0500
From: email@example.com (Marc Andreessen)
To: Mowgli C Assor <firstname.lastname@example.org>
Subject: Postscript Behavior...
Mowgli C Assor writes:
> Um, I've been playing with various ways of getting postscript to display
> via XMosaic (1.0). When you use FTP, things are fine, because the FTP daemon
> doesn't do any processing, and so when XMosaic hands off to Ghostview or
> whatever, life is fine.
> However, when HTTP processes the file, it puts the line :
> in front of the rest of the document. Thus, when it gets back to Ghostview,
> it chokes because <PLAINTEXT> is invalid PS. This may again get us to the
> point of needing "type tags" for different types of files, but with the
> coming various "multi-media" browsers, it seems to me to be a problem we
> need to solve somehow (perhaps the URLs will help, but I don't think they
> are the ultimate solution).
> I can just set up a filter for Ghostscript which removes the offending
> line, but is there a better solution?
The long-term solution is to move to HTTP2. One short-term solution
that you may want to explore is the NCSA public domain httpd, on
ftp.ncsa.uiuc.edu in /Mosaic/ncsa_httpd, which will never do this to
Software Development Group
National Center for Supercomputing Applications