Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Vulnerability Development: RE: Plain text files in internet explorer

RE: Plain text files in internet explorer

From: Bernie Cosell <bernie_at_fantasyfarm.com>
Date: Sun, 1 Sep 2002 18:19:34 -0400

On 1 Sep 2002, at 14:47, Alan Ramsbottom wrote:

> John Hennessy [mailto:johnh_at_charm.net wrote:
>
> > Is it just me or is impossible to have plain text in internet
> > explorer?
>
> It's everyone. Read all about it (datasniffing) here:
>
> http://msdn.microsoft.com/library/default.asp?url=/workshop/networking/m
> oniker/overview/appendix_a.asp
>
> "A MIME type is ambiguous if it is 'text/plain',
> 'application/octet-stream', an empty string, or null (that is, the
> server failed to provide it)."

Is this actually specified someplace in some relevant RFC? I can't
comment on application/octet-stream, but I've never before heard that
text/plain was ambiguous. I thought it was crystal-clear and meant,
well, "plain text" [basically a sequence of characters in whatever
charset is specified].

Is this interpretation some idiosyncracy of Microsoft's or is it actually
an RFC-supported 'correct' interpretation of the text/plain MIME type?

  /Bernie\

-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie_at_fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--          
Received on Sep 01 2002
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos