Hi Werner,

there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere.

The only thing you can do is to check the console.log in your browser ...

JM

On 8 Feb 2020, at 09:17, Werner Joss werner@hoernerfranzracing.de wrote:

I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant: I can no longer log into my infcloud instance as the Login screen is just empty. Looking in the page source in the Browser, I see that all containers have the attribute display:none Especially also

<><div id="LoginPage" style="opacity: 1; display:none">

What could I try to solve this ?

Hi Werner,

mime types are returned by your web server (e.g. Apache). There is a web server config which says something like:

.html text/html .txt text/plain .js text/javascript ... ...

It looks like your web server (which returns the static javascript files) thinks that .js is text/html => it is 100% server configuration problem (NOT CardDAV/CalDAV server and NOT InfCloud client configuration).

Also don't forget to execute the cache_update.sh after every change of your web server config (because your browser can cache the old headers even if the server returns the correct ones after you fixed your the server config).

JM

On 9 Feb 2020, at 10:18 AM, Werner Joss werner@hoernerfranzracing.de wrote:

Hi Jan, Thanks for reply - and no, I did not change anything since it used to work. But from the browser console output, I suppose the configuration is not loaded correctly, see the attached screenshot, Telling me the MIME type of file config.js is wrong. As a result, globalInterfaceLanguage is not defined in main.js In config.js, the corresponding line is

var globalInterfaceLanguage='de_DE';

I'm not sure how to change the MIME type of config.js ?

Werner

Am Samstag, 8. Februar 2020, 19:59:22 CET schrieb Ján Máté:

...

Hi Werner, there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere. The only thing you can do is to check the console.log in your browser ... JM

...

...

...

On 8 Feb 2020, at 09:17, Werner Joss werner@hoernerfranzracing.de wrote:

I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant: I can no longer log into my infcloud instance as the Login screen is just empty. Looking in the page source in the Browser, I see that all containers have the attribute display:none Especially also <><div id="LoginPage" style="opacity: 1; display:none"> What could I try to solve this ?

Hi Werner,

the problem is NOT in your config.js, there is NO MAGIC. The web server DOES NOT check the content of this file. The server returns the MIME type by checking the file NAME (not content).

Use the following command in terminal (the "-crlf" depends on your server):

openssl s_client -crlf -connect www.somesite.com:443

then use the following commands (as usually for telnet www.somesite.com 80):

GET /infcloud/config.js HTTP/1.1 Host: www.somesite.com

and you will get something like:

HTTP/1.1 200 OK Date: Sun, 09 Feb 2020 10:57:09 GMT Server: Apache Last-Modified: Tue, 22 Sep 2015 13:30:13 GMT ETag: "d702-52055ff73d2cd" Accept-Ranges: bytes Content-Length: 55042 Vary: Accept-Encoding Cache-Control: max-age=0, must-revalidate, no-cache, no-transform, private Expires: Sun, 09 Feb 2020 10:57:09 GMT Strict-Transport-Security: max-age=15768000 Content-Type: application/javascript

<content of the config.js>

The content type is the line which must be set correctly! If the Content-type will be correct in the response, then it will work also in your browser (after forcing it to clear the cache by executing the cache_update.sh).

JM

On 9 Feb 2020, at 11:24, Werner Joss werner@hoernerfranzracing.de wrote:

..just an additional note: I noticed that the file /etc/mime.types has been changed on Jan 28, obviously by my hoster (I have no write access in /etc) and this corresponds well with The date from which infcloud would no more work for me. The file, however, contains a line

application/javascript js

Which seems ok, but maybe there is another (new) magic thing which now prevents config.js to be recognized as javascript instead of text/plain ? I'm just thinking about pasting everything which is not commented out from config.js into the beginning of main.js (which is obviuosly considered to be javascript) And then just comment out loading config.js in index.html ?

am Sonntag, 9. Februar 2020, 10:10:30 CET schrieb Werner Joss:

...

Hi Jan, Thanks for reply - and no, I did not change anything since it used to work. But from the browser console output, I suppose the configuration is not loaded correctly, see the attached screenshot, Telling me the MIME type of file config.js is wrong. As a result, globalInterfaceLanguage is not defined in main.js In config.js, the corresponding line is

var globalInterfaceLanguage='de_DE';

I'm not sure how to change the MIME type of config.js ?

Werner

Am Samstag, 8. Februar 2020, 19:59:22 CET schrieb Ján Máté:

...

Hi Werner,

there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere.

The only thing you can do is to check the console.log in your browser ...

JM

...

On 8 Feb 2020, at 09:17, Werner Joss werner@hoernerfranzracing.de wrote:

I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant: I can no longer log into my infcloud instance as the Login screen is just empty. Looking in the page source in the Browser, I see that all containers have the attribute display:none Especially also

<><div id="LoginPage" style="opacity: 1; display:none">

What could I try to solve this ?

Hello Werner,

I was wondering - could there be some overriding setting on your server latching onto the "config" part of the filename and declaring everything that matches a text file, even if it ends in ".js"...? If so, simply renaming config.js to anything else (including all references to it of course) might make the difference...

Best of luck,    Max

On 09-02-2020 13:21, Werner Joss wrote:

Hello Jan, Yes, I'm well aware that the problem is caused by an obviously changed configuration on the server. But, as this is a cheap shared hosting deal, I have no access to the server config.

Now, after fiddling around some more, I got it to work again, by just copying everything from config.js that was not commented out to the very beginning of file main.js And then changing index.html to not load config.js.

I know that this is a very ugly hack, but I'm afraid I have no other choice.

Thanks again for your support - I also tried the proposed verification via openssl from your last mail, which did not work for some reason, But it is clear that the server just returns the wrong MIME type for config.js, whereas main.js and others are recognized correctly.

Werner

Am Sonntag, 9. Februar 2020, 11:03:08 CET schrieb Ján Máté:

...

Hi Werner,

mime types are returned by your web server (e.g. Apache). There is a web server config which says something like:

.html text/html .txt text/plain .js text/javascript ... ...

It looks like your web server (which returns the static javascript files) thinks that .js is text/html => it is 100% server configuration problem (NOT CardDAV/CalDAV server and NOT InfCloud client configuration).

Also don't forget to execute the cache_update.sh after every change of your web server config (because your browser can cache the old headers even if the server returns the correct ones after you fixed your the server config).

JM

...

On 9 Feb 2020, at 10:18 AM, Werner Joss werner@hoernerfranzracing.de wrote:

Hi Jan, Thanks for reply - and no, I did not change anything since it used to work. But from the browser console output, I suppose the configuration is not loaded correctly, see the attached screenshot, Telling me the MIME type of file config.js is wrong. As a result, globalInterfaceLanguage is not defined in main.js In config.js, the corresponding line is

var globalInterfaceLanguage='de_DE';

I'm not sure how to change the MIME type of config.js ?

Werner

Am Samstag, 8. Februar 2020, 19:59:22 CET schrieb Ján Máté:

...

Hi Werner, there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere. The only thing you can do is to check the console.log in your browser ... JM

...

...

> On 8 Feb 2020, at 09:17, Werner Joss werner@hoernerfranzracing.de wrote: I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant: I can no longer log into my infcloud instance as the Login screen is just empty. Looking in the page source in the Browser, I see that all containers have the attribute display:none Especially also <><div id="LoginPage" style="opacity: 1; display:none"> What could I try to solve this ?

Hello Max, Thanks for your suggestion, but I doubt it will work - changing the name of config.js to something else, e.g. config.txt, will surely prevent it to be loaded as javascript via index.html (this is the only place where it is referenced), even more than now :) But, as stated, I have already a solution - not elegant, I know, but it works.

Werner

Am Sonntag, 9. Februar 2020, 15:08:27 CET schrieb Attila Asztalos:

Hello Werner,

I was wondering - could there be some overriding setting on your server latching onto the "config" part of the filename and declaring everything that matches a text file, even if it ends in ".js"...? If so, simply renaming config.js to anything else (including all references to it of course) might make the difference...

Best of luck, Max

On 09-02-2020 13:21, Werner Joss wrote:

...

Hello Jan, Yes, I'm well aware that the problem is caused by an obviously changed configuration on the server. But, as this is a cheap shared hosting deal, I have no access to the server config.

Now, after fiddling around some more, I got it to work again, by just copying everything from config.js that was not commented out to the very beginning of file main.js And then changing index.html to not load config.js.

I know that this is a very ugly hack, but I'm afraid I have no other choice.

Thanks again for your support - I also tried the proposed verification via openssl from your last mail, which did not work for some reason, But it is clear that the server just returns the wrong MIME type for config.js, whereas main.js and others are recognized correctly.

Werner

Am Sonntag, 9. Februar 2020, 11:03:08 CET schrieb Ján Máté:

...

Hi Werner,

mime types are returned by your web server (e.g. Apache). There is a web server config which says something like:

.html text/html .txt text/plain .js text/javascript ... ...

It looks like your web server (which returns the static javascript files) thinks that .js is text/html => it is 100% server configuration problem (NOT CardDAV/CalDAV server and NOT InfCloud client configuration).

Also don't forget to execute the cache_update.sh after every change of your web server config (because your browser can cache the old headers even if the server returns the correct ones after you fixed your the server config).

JM

...

On 9 Feb 2020, at 10:18 AM, Werner Joss werner@hoernerfranzracing.de wrote:

Hi Jan, Thanks for reply - and no, I did not change anything since it used to work. But from the browser console output, I suppose the configuration is not loaded correctly, see the attached screenshot, Telling me the MIME type of file config.js is wrong. As a result, globalInterfaceLanguage is not defined in main.js In config.js, the corresponding line is

var globalInterfaceLanguage='de_DE';

I'm not sure how to change the MIME type of config.js ?

Werner

Am Samstag, 8. Februar 2020, 19:59:22 CET schrieb Ján Máté:

...

Hi Werner, there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere. The only thing you can do is to check the console.log in your browser ... JM

...

>> On 8 Feb 2020, at 09:17, Werner Joss werner@hoernerfranzracing.de wrote: > I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant: > I can no longer log into my infcloud instance as the Login screen is just empty. > Looking in the page source in the Browser, I see that all containers have the attribute display:none > Especially also > <><div id="LoginPage" style="opacity: 1; display:none"> > What could I try to solve this ?