Re: Re: Change in 5.2.1 re. parsing of URL

Lewis Kapell wrote: > We are already using the Content-type header (I should have mentioned > that in my first message). Hmmm. So you have a PHP script that sets the mimetype correctly and then outputs straight PDF data, but the user's browser does not accept it as a PDF because the extension of the script is PHP? I find that strange. If you can't find a better solution (something weird is going on in my mind) maybe a work-around is mod_rewrite? You could link to the PHP script with a PDF extension and then rewrite it to the PHP extension behind the scenes. > And to say that the user's browser is misconfigured is no solution, > since we don't have the ability to reconfigure it. If all of our > users were on a local network there would be no problem. But that's > not our situation. I agree it's not a solution, but client misconfiguration is difficult, often impossible, to solve with server-side scripting. If you could identify the misconfiguration, your site could offer a how-to document to instruct users how to configure their software correctly.