Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.javascript
Subject: Re: IIS http.open "GET" error
Date: Fri, 9 Oct 2020 23:49:49 +0200
Lines: 25
Message-ID: <huc47tF4jgoU4@mid.individual.net>
References: <ebdc63ad-7565-4d6e-872e-90c9a8719f70o@googlegroups.com> <huaqreFqk7fU1@mid.individual.net> <rlpvrv$h67$1@solani.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net HJv0CMOlmRi3xZjjRq6RlgLhlTY5fGbC55Jr7W9hQbDtMj2toT
Cancel-Lock: sha1:woIR23wzHykp5Kj671WOBXryBnM=
In-Reply-To: <rlpvrv$h67$1@solani.org>
Xref: csiph.com comp.lang.javascript:38923

Frank Kozuschnik:

> Arno Welzel:
> 
>> 1) Make sure IIS works at all - put the file named SPASSKY.JCH to the
>> root directory and check that http://localhost/SPASSKY.JCH or
>> http://127.0.0.1/SPASSKY.JCH gives you the content of that file.
> 
> In a default setup, IIS will return a HTTP 404 error because the '.JCH' 
> suffix ("extension") is unknown. Adding the suffix to the "MIME Types" 
> list of the IIS configuration may help.

Is IIS really that stupid not to send the content of a file just because
it does not know the extension? One more reason not to use such crap. Go
and get NGINX or Apache - these are also available for Windows:

<https://httpd.apache.org/docs/2.4/platform/windows.html>

<http://nginx.org/en/docs/windows.html>



-- 
Arno Welzel
https://arnowelzel.de