Clarence wrote: >No, I don't think that is the first step, because, as you point out, a lot >of servers send EVERYTHING as text/plain. :(( >I have asked Michael to consider allowing the extension to take priority >over mime type so we can get around these server problems in many areas. >His response was, "that's the way the other browsers do it but it is >improper use of the standards". Ahem, that's the way Internet Explorer does it. And pre 4.x (IIRC) versions of Netscape treated HTML in text files as well. My suggestion is that Arachne should assume the correct MIME type has been sent unless text/plan comes along and then check to see what the extension is. //Bernie
- (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF Clarence Verge
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF Clarence Verge
- Re: (OT) Re: Unisys & GIF Dale Mentzer
- Re: (OT) Re: Unisys & GIF L.D. Best
- Re: (OT) Re: Unisys & GIF Clarence Verge
- Re: (OT) Re: Unisys & GIF Bernie
- Re: (OT) Re: Unisys & GIF Bernie
- Re: (OT) Re: Unisys & GIF Bernie
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF J. J. Young
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
- Re: (OT) Re: Unisys & GIF Clarence Verge
- Re: (OT) Re: Unisys & GIF Ben Hood
- Re: (OT) Re: Unisys & GIF Glenn McCorkle
