It's struck me that there are two different situations for content-typesniffing in web agents: when the web browser knows that it is requestinga specific sort of thing, and when it can have no expectations aboutwhat it will get. The first situation happens when the browser is doingthings like loading CSS stylesheets or retrieving inlined images; thesecond situation usually happens when the user clicks on a link.
When the browser knows what it is supposed to be getting, it alreadyknows what it's trying
Because someone quoted me , I mightas well explain my earlier quick comment about how I consider the lack of a Debian package for a program to be afairly serious warning sign, and why I specifically picked Debian forthis.
Debian has a huge package selection with a fairly large number of peopledriving it. If a program is still not packaged for Debian, this meansthat either that it can't attract even one Debian developer's interestor that the program has serious issues of some sort; immaturity,
Someone around here recently asked me my opinions on Solaris on x86machines, and in thinking about it I decided I might as well put downmy current thoughts on the whole matter.
First, we're no longer interested in SPARC hardware and thus SPARCSolaris. The hardware is clearly no longer competitive for genericcomputing; it may be competitive in some niche roles, but my area doesn't have any of those niches we needfilled.
(In the long run I feel that a retreat to specialized
Copyright/left
Standards
Update
Tips/Tools
There are two parties that could be responsible for determining whattype of content you are getting in a HTTP response, whether the data isHTML or a PDF or a JPEG or so on: the server or the client. The web hasopted to make it determined by the server ,and this is the correct place for a simple reason: consistency .
Imagine a world where the clients determine what the content type is.If there is no standard for how clients determine the content type, theconsistency problems are obvious;