Cecil Moore wrote:
Michael Coslo wrote:
A Different server or ISP. An EZ solution......

I should have requested a Linux server, not a
Microsoft server. :-) But the problem has been
solved.

Good to see it solved, Cecil. I much prefer to run things off a Linux
server, seems to be less problems overall. I've always hosted in Linux,
but My son went with Windows for a while, and eventually changed to
Linux after nothing he wanted to do worked.


- 73 de Mike KB3EIA -

Owen Duffy wrote:
If I click on Cecil's link, I get a 404 error: file not found which is a
strong indicator the file is not there, or has incorrect permissions,
probably the former.

Not to pick on Owen as an individual, but rather on gurus
in general:

This is an example of the combination of arrogance and
ignorance often exhibited by gurus. As a matter of fact,
the most probable explanation was that a file type had
not been defined on a Microsoft server. Ignorance of
Microsoft servers was the problem, not that the file
was not there.

But don't hold your breath for: "Thanks, I was wrong
and I learned something today." from any guru.
--
73, Cecil http://www.w5dxp.com

"Jeff" wrote in
. com:


" Apart from special processing specified for some files or file
types
(extensions), the server just sends the document back in a response
under http headers (some of which may be chosen based on extension -
MIME type association in the server's config files.

I suspect that it is this part that is going wrong, there is no
association for a .ez extension and the server is responding with a
404 error. Hence the request for a MIME type.

You obviously don't know how web servers, HTTP, and browsers work.

Owen

Michael Coslo wrote in news:f1tahl$1218$1
@f04n12.cac.psu.edu:

Cecil Moore wrote:
Michael Coslo wrote:
A Different server or ISP. An EZ solution......

I should have requested a Linux server, not a
Microsoft server. :-) But the problem has been
solved.

Good to see it solved, Cecil. I much prefer to run things off a Linux
server, seems to be less problems overall. I've always hosted in Linux,
but My son went with Windows for a while, and eventually changed to
Linux after nothing he wanted to do worked.

Is the issue the operating system, or the web server. In other words, is
it Windows Vs Linux, or IIS vs Apache? (You can run Apache on Windows.)

It is a long time since I looked after IIS, but then it wasn't a patch on
Apache (if you will pardon the pun... an it is a pun as the name Apache
(with the stange spelling) is a shortening of "a patchy server",
reflecting its origins).

Owen

Owen Duffy wrote:
"Jeff" wrote in
I suspect that it is this part that is going wrong, there is no
association for a .ez extension and the server is responding with a
404 error. Hence the request for a MIME type.

You obviously don't know how web servers, HTTP, and browsers work.

Your ignorance and arrogance are showing again, Owen.
Jeff obviously knows exactly how Microsoft servers work.
--
73, Cecil http://www.w5dxp.com

Owen Duffy wrote:
Is the issue the operating system, or the web server.

Apparently, it was a Microsoft operating system problem.
--
73, Cecil http://www.w5dxp.com

On Wed, 09 May 2007 21:50:34 GMT, Cecil Moore
wrote:

Owen Duffy wrote:
"Jeff" wrote in
I suspect that it is this part that is going wrong, there is no
association for a .ez extension and the server is responding with a
404 error. Hence the request for a MIME type.

"web servers are configured to report a MIME type of text/plain
for unknown content types"

You obviously don't know how web servers, HTTP, and browsers work.

Your ignorance and arrogance are showing again, Owen.

And this is from someone who has never written a line of code for
desinging a server.

Jeff obviously knows exactly how Microsoft servers work.

So, the server is asking (which is what request means) the client for
the MIME type? What a yuk. And using M$ as the gold standard for
providing non-HTTP compliant servers? Yuk² Quite literally, M$ does
not know how HTTP servers are supposed to work.

"MIME is currently defined in RFCs 2045, 2046, 2047, 2048, and
2049 and registered values for MIME types are available in IANA |
MIME Media Types. The HTTP specification defines a superset of
MIME which is used to describe the media types used on the web."

M$ does not conform.

Source:
http://developer.mozilla.org/en/docs...ver_MIME_Types

From one who has written many servers - myself.

Richard Clark wrote:
And this is from someone who has never written a line of code for
desinging a server.

It would never occur to me that a line of code to make
a server stop singing was required. How did you stumble
upon that pressing need?
--
73, Cecil http://www.w5dxp.com

On Wed, 09 May 2007 22:23:06 GMT, Cecil Moore
wrote:

How did you stumble
upon that pressing need?

Only a pants-presser would be worried about that.

Richard Clark wrote in
:

....
Jeff obviously knows exactly how Microsoft servers work.

So, the server is asking (which is what request means) the client for
the MIME type?

I doubt it.

What a yuk. And using M$ as the gold standard for
providing non-HTTP compliant servers? Yuk² Quite literally, M$ does
not know how HTTP servers are supposed to work.

"MIME is currently defined in RFCs 2045, 2046, 2047, 2048, and
2049 and registered values for MIME types are available in IANA |
MIME Media Types. The HTTP specification defines a superset of
MIME which is used to describe the media types used on the web."

While some are stressing about getting IANA registration of the ez
extension, it already is, and to another application, and its type is
application/andrew-inset.

So, many web servers (using the IANA MIME media type list) will serve the
file up with a HTTP Content-Type of application/andrew-inset . That won't
affect most users, because their browser will not have any defined action
for that application type.

On a good web server, one could override that MIME association for the
file, files, directory or tree... but it shouldn't be necessary.

Owen