Hi Jay,
Jay Jacobs wrote:
> I've got a form that will (should) send various formats back to the client
> depending on form values. They may want the results back in csv, pdf or
> plain html. The form always submits to a .html, and the browser usually
> expects an html.
> I've tried setting $r->content_type and even $r->filename to try and get
> the browser (ie 5 for now) to see it as a non-html file and "do the
> right thing". Then I came across setting "Content-Disposition":
Be careful with IE5 and expecting it to honor MIME types. IE5 will
actually analyze the data being sent over and determiner whether or not the
MIME type is appropriate. (See
msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.asp for
more details.) To get around IE5's funky behavior just defined a custom MIME
type outside the MS hardcoded stuff.
> I've never run across
> Content-Disposition, anyone have a listing of what it does and the
> options?
See RFC 1806 and RFC 2183 for details about Content-Disposition. But bear
in mind that RFC 2616 (HTTP/1.1 spec) explicitly says that using
Content-Disposition is a bad thing (section 15.5.)
HTH.
John
--
+----------------------------I speak for myself.----------------------------+
| John Jung ([EMAIL PROTECTED]) | Unigraphics Solutions |
| Global Technical Access Center | 10824 Hope Street, Cypress Pointe |
| Operating Systems Group | Cypress, California 90630 |
+------------------------------(800) 955-0000-------------------------------+
