|
|
Posted by Jasper Bryant-Greene on 10/21/16 11:21
Dotan Cohen wrote:
> On 7/16/05, Lauri Harpf <svr.tuomas@kolumbus.fi> wrote:
>>I've been thinking of limiting this problem by preventing the direct
>>displaying of the code (ie. only allowing "Save As.." for the link to the
>>user-submitted HTML). I guess a bit of JS could prevent accidental
>>left-clicking on the link. I've also been thinking of passing a special
>>header for the HTML source code file, "Content-type:
>>application/octet-stream" to suggest downloading rather than displaying the
>>contents, but IE seems to just ignore it and display the HTML anyhow.
Something like this (you might like to check the syntax, I'm working
from memory here) might work:
header('Content-Disposition: attachment; filename=somefile.html');
> Forgot trying to work around IE. The browser is broken. It is
> non-standard. It's bugs are not fixed. The more you bang your head
> against the wall trying to fix what is Microsoft's responsibility to
> fix, the less reason people will have to switch to a non-broken
> browser (or OS!). Let them use a standards-compliant web browser.
If only we lived in such a perfect world... remember that the majority
of web users use IE, so unless you enjoy shutting out the majority of
your customers, we do need to work around it.
Let's not get this thread OT though.
Jasper
Navigation:
[Reply to this message]
|